From: Simon Schubert <2@0x2c.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: BUG in skb_dequeue (skb->next is NULL)
Date: Wed, 01 Dec 2010 11:34:36 +0100 [thread overview]
Message-ID: <4CF624BC.8030409@0x2c.org> (raw)
In-Reply-To: <1291199299.2856.499.camel@edumazet-laptop>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
prev parent reply other threads:[~2010-12-01 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1011071631550.2636@dyndns.pervalidus.net>
[not found] ` <loom.20101201T095252-592@post.gmane.org>
2010-12-01 10:28 ` BUG in skb_dequeue (skb->next is NULL) (was: Re: Kernel crash with 2.6.36) Eric Dumazet
2010-12-01 10:34 ` Simon Schubert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CF624BC.8030409@0x2c.org \
--to=2@0x2c.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).