Re: Invalid sk_policy[] access (was Re: Recent spontaneous reboots on multiple machines)

2016-02-23 Thread Meelis Roos
> > However, I have not succeeded in reproducing the problem at will - git > > checkout of another release + subsequent compile still does not trigger > > it. But if it is the same problem, it seems to go int triple fault or > > something similar for me to cause it reboot with no trace in the >

Re: Invalid sk_policy[] access (was Re: Recent spontaneous reboots on multiple machines)

2016-02-23 Thread Meelis Roos
> I figured out what's the root-cause of my panics. Great! > sizeof 32-bit64-bit > --- > request_sock 256 312 > inet_request_sock 272 328 > sock 688 1216 > > And offsetof sk_p

Re: Invalid sk_policy[] access (was Re: Recent spontaneous reboots on multiple machines)

2016-02-23 Thread Sowmini Varadhan
On (02/23/16 21:36), Meelis Roos wrote: > Sorry, I do not understand - what is 32-bit on V440? The kernel should > be 64-bit since it's sun4u. v440# getconf LONG_BIT 32 v440# uname -a Linux v440 4.4.0-rc3-roos-00790-g264a4ac-dirty #200 SMP Mon Feb 22 19:06:21 PST 2016 sparc64 GNU/Linux > Howe

Invalid sk_policy[] access (was Re: Recent spontaneous reboots on multiple machines)

2016-02-23 Thread Sowmini Varadhan
I figured out what's the root-cause of my panics. In my case, for the stack shown in http://marc.info/?l=linux-sparc&m=145610295109214&w=2 (which also has all the details about the issue), tcp_make_synack has been called with attach_req set to true so it sets up the skb->sk via: if (a