From: Manfred Spraul <manfred@colorfullife.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: cboulte@gmail.com, Nadia.Derbey@bull.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SYSVIPC - Fix the ipc structures initialization
Date: Wed, 12 Nov 2008 07:41:47 +0100 [thread overview]
Message-ID: <491A7AAB.2070103@colorfullife.com> (raw)
In-Reply-To: <20081111141603.f0e7fa8d.akpm@linux-foundation.org>
Andrew Morton wrote:
>> I don't understand what's going on... I hope I'm not the only one who
>> still get it because I doubt about this bug.
>>
One thing is odd:
The test app uses fork(), two processes.
One process constantly does
msgctl(0, IPC_STAT, &buf);
The other process creates a new msg queue, then it destroys it.
But: The probablity that the new queue has the msqid is 0 is tiny
[impossible?].
That means the idr_find() call should [must?] fail.
But then the spin_lock() should never be executed. Why do you get an
oops in that call?
Do you still use the test app that is on bugzilla?
>>
>
> Time is starting to press on this one. Is there something which we can
> revert which would fix this bug?
>
> Thanks.
>
next prev parent reply other threads:[~2008-11-12 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081028145952.620752409@bull.net>
2008-10-28 14:59 ` [PATCH] SYSVIPC - Fix the ipc structures initialization Nadia.Derbey
2008-10-28 17:22 ` Manfred Spraul
2008-10-29 9:11 ` cboulte
2008-11-11 22:16 ` Andrew Morton
2008-11-12 6:41 ` Manfred Spraul [this message]
2008-11-13 6:10 ` Manfred Spraul
2008-11-13 8:06 ` Peter Zijlstra
2008-11-13 10:08 ` Nadia Derbey
2008-11-13 17:53 ` Manfred Spraul
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=491A7AAB.2070103@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=cboulte@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).