From: Andrew Morton <akpm@linux-foundation.org>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: Nadia.Derbey@bull.net, adobriyan@sw.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm1 1/2] fixing idr_find() locking
Date: Thu, 27 Sep 2007 23:39:44 -0700 [thread overview]
Message-ID: <20070927233944.347aaecd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070928063144.GB1767@ff.dom.local>
On Fri, 28 Sep 2007 08:31:44 +0200 Jarek Poplawski <jarkao2@o2.pl> wrote:
> On Thu, Sep 27, 2007 at 04:33:55PM +0200, Nadia.Derbey@bull.net wrote:
> > [PATCH 01/02]
> >
> >
> > This is a patch that fixes the way idr_find() used to be called in ipc_lock():
> > in all the paths that don't imply an update of the ipcs idr, it was called
> > without the idr tree being locked.
> >
> > The changes are:
> > . in ipc_ids, the mutex has been changed into a reader/writer semaphore.
> > . ipc_lock() now takes the mutex as a reader during the idr_find().
> > . a new routine ipc_lock_down() has been defined: it doesn't take the
> > mutex, assuming that it is being held by the caller. This is the routine
> > that is now called in all the update paths.
> >
> >
> > Signed-off-by: Nadia Derbey <Nadia.Derbey@bull.net>
>
> Acked-by: Jarek Poplawski <jarkao2@o2.pl>
thanks.
> PS: there is one big mistake around To/Cc ordering, so I doubt Andrew
> will ever sign this...
Noe, I received and applied it earlier today.
next prev parent reply other threads:[~2007-09-28 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 14:33 [PATCH -mm1 0/2] Fix unlocked call to idr_find() Nadia.Derbey
2007-09-27 14:33 ` [PATCH -mm1 1/2] fixing idr_find() locking Nadia.Derbey
2007-09-28 6:31 ` Jarek Poplawski
2007-09-28 6:39 ` Andrew Morton [this message]
2007-09-28 7:08 ` Nadia Derbey
2007-09-28 7:34 ` Jarek Poplawski
2007-09-27 14:33 ` [PATCH -mm1 2/2] Removing unneeded parameters Nadia.Derbey
2007-09-28 5:52 ` [PATCH -mm1 0/2] Fix unlocked call to idr_find() Jarek Poplawski
2007-09-28 6:12 ` Nadia Derbey
2007-09-28 6:41 ` Jarek Poplawski
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=20070927233944.347aaecd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Nadia.Derbey@bull.net \
--cc=adobriyan@sw.ru \
--cc=jarkao2@o2.pl \
--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