[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AA5E717.1050002@in.ibm.com>
Date: Tue, 08 Sep 2009 10:39:43 +0530
From: Sachin Sant <sachinp@...ibm.com>
To: Eric Dumazet <eric.dumazet@...il.com>
CC: netdev <netdev@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: Re: Next Sept 7: Bug : skb_release_head_state on x86
Eric Dumazet wrote:
> and you decode a 64 bits kernel
>
OOPS. Sorry about that. I had next running on 32 and 64
bit machines and goofed up while collecting the disassembly.
> This is more probably
>
> <f0> ff 0a lock decl (%edx)
>
> part of :
>
> secpath_put(skb->sp);
>
Yup this is what shows up when looking at correct disassembly.
>
> So some skb has a strange/buggy skb->sp (value 0x00010090)
>
> It looks like skb->cb[xxx] overwrote skb->sp
>
> Please check you have CONFIG_XFRM=y, and that you did rebuild all your modules after
> patching your kernel...
>
Yes, CONFIG_XFRM is enabled. Earlier next kernels did not have this problem.
The last one i tried successfully was 0902. 0904 had some build failure
(related to net/3c503.c) hence could not boot test that.
Will try to boot 0904 and will check if the same problem can be recreated.
I have attached the config file used.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
View attachment "config_next0907" of type "text/plain" (95334 bytes)
Powered by blists - more mailing lists