From: Manfred Spraul <manfred@colorfullife.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Harald Laabs <kernelml@dasr.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] null-pointer in task_rq_lock (2.6.35 to 3.0-rc7)
Date: Wed, 20 Jul 2011 20:11:50 +0200 [thread overview]
Message-ID: <4E271A66.40307@colorfullife.com> (raw)
In-Reply-To: <1311110082.3113.27.camel@edumazet-laptop>
On 07/19/2011 11:14 PM, Eric Dumazet wrote:
> Le mardi 19 juillet 2011 à 22:03 +0200, Harald Laabs a écrit :Hi,
>>
>> I'm not able to fix or understand this bug myself, its already in
>> bugzilla with the call trace:
>> https://bugzilla.kernel.org/show_bug.cgi?id=27142
>>
>> Is there any more useful information I can provide? Anything to test?
Could you build a kernel with CONFIG_DEBUG_LIST enabled?
Does it report anything?
>> Does anyone know of changes from 2.6.34 to 2.6.35 that might have
>> broken this? (The diff and the changelog do not enlighten me, too
>> much changed and I understand little of it.)
> I feel commit 0a2b9d4c79671b059568 might be the bug origin
> (ipc/sem.c: move wake_up_process out of the spinlock section)
>
I'll try to reproduce the bug tomorrow.
Perhaps a race with multiple processes sleeping, some/all woken up by a
signal an a concurrent IPC_RM.
But I don't see the bug yet.
--
Manfred
next prev parent reply other threads:[~2011-07-20 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 20:03 [BUG] null-pointer in task_rq_lock (2.6.35 to 3.0-rc7) Harald Laabs
2011-07-19 21:14 ` Eric Dumazet
2011-07-20 18:11 ` Manfred Spraul [this message]
2011-08-15 7:22 ` scream
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=4E271A66.40307@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=kernelml@dasr.de \
--cc=linux-kernel@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