Message-ID: <491A7AAB.2070103@colorfullife.com>
Date: Wed, 12 Nov 2008 07:41:47 +0100
From: Manfred Spraul <manfred@colorfullife.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
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
References: <20081028145952.620752409@bull.net> <20081028150041.857635775@bull.net> <4f3ee3290810290211y75a2d0eaoe666496e25496260@mail.gmail.com> <20081111141603.f0e7fa8d.akpm@linux-foundation.org>
In-Reply-To: <20081111141603.f0e7fa8d.akpm@linux-foundation.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 991
Lines: 31

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.
>   

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/