Messages in this thread | | | Date | Wed, 01 Dec 2010 11:34:36 +0100 | From | Simon Schubert <> | Subject | Re: BUG in skb_dequeue (skb->next is NULL) |
| |
On 12/01/2010 11:28 AM, Eric Dumazet wrote: > Le mercredi 01 décembre 2010 à 09:02 +0000, Simon Schubert a écrit : >> Frédéric L. W. Meunier <2 <at> pervalidus.net> writes: > > CC netdev >> RIP: 0010:[<ffffffff81459069>] [<ffffffff81459069>] skb_dequeue+0x59/0x90 >> Call Trace: >> [<ffffffff814ef0fa>] unix_stream_recvmsg+0x1aa/0x790 >> [<ffffffff8145124d>] sock_recvmsg+0xfd/0x130 >> [<ffffffff81155fd0>] ? pollwake+0x0/0x60 >> [<ffffffff81452b54>] __sys_recvmsg+0x144/0x2e0 >> [<ffffffff81155fd0>] ? pollwake+0x0/0x60 >> [<ffffffff8104d88a>] ? finish_task_switch+0x4a/0xd0 >> [<ffffffff8154fa91>] ? schedule+0x411/0xa50 >> [<ffffffff81452f99>] sys_recvmsg+0x49/0x80 >> [<ffffffff8100b0b2>] system_call_fastpath+0x16/0x1b > > Is it reproductible ?
I can't trigger it on purpose, but it happened two nights in a row (I don't have the previous backtrace though)
> On previous kernel (say 2.6.35) you never hit this bug ?
No.
cheers simon
[unhandled content-type:application/pgp-signature] | |