From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Jan Blunck <jblunck@suse.de>,
Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] atomic: Only take lock when the counter drops to zero on UP as well
Date: Tue, 14 Apr 2009 09:48:39 -0700 [thread overview]
Message-ID: <20090414164839.GI6753@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090414065239.GA20951@wotan.suse.de>
On Tue, Apr 14, 2009 at 08:52:39AM +0200, Nick Piggin wrote:
> On Fri, Apr 10, 2009 at 06:13:57PM +0200, Jan Blunck wrote:
> > I think it is wrong to unconditionally take the lock before calling
> > atomic_dec_and_test() in _atomic_dec_and_lock(). This will deadlock in
> > situation where it is known that the counter will not reach zero (e.g. holding
> > another reference to the same object) but the lock is already taken.
> >
> > Signed-off-by: Jan Blunck <jblunck@suse.de>
>
> Paul's worry about callers aside, I think it is probably a good idea
> to reduce ifdefs and share more code.
I am also OK with this patch.
Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> So for this patch,
>
> Acked-by: Nick Piggin <npiggin@suse.de>
>
> > ---
> > lib/dec_and_lock.c | 3 +--
> > 1 files changed, 1 insertions(+), 2 deletions(-)
> >
> > diff --git a/lib/dec_and_lock.c b/lib/dec_and_lock.c
> > index a65c314..e73822a 100644
> > --- a/lib/dec_and_lock.c
> > +++ b/lib/dec_and_lock.c
> > @@ -19,11 +19,10 @@
> > */
> > int _atomic_dec_and_lock(atomic_t *atomic, spinlock_t *lock)
> > {
> > -#ifdef CONFIG_SMP
> > /* Subtract 1 from counter unless that drops it to 0 (ie. it was 1) */
> > if (atomic_add_unless(atomic, -1, 1))
> > return 0;
> > -#endif
> > +
> > /* Otherwise do it the slow way */
> > spin_lock(lock);
> > if (atomic_dec_and_test(atomic))
> > --
> > 1.6.0.2
next prev parent reply other threads:[~2009-04-14 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 16:13 [PATCH] atomic: Only take lock when the counter drops to zero on UP as well Jan Blunck
2009-04-11 17:49 ` Paul E. McKenney
2009-04-12 11:32 ` Jan Blunck
2009-04-13 6:02 ` Paul E. McKenney
2009-04-22 12:56 ` Jan Blunck
2009-04-22 14:08 ` Paul E. McKenney
2009-04-14 6:52 ` Nick Piggin
2009-04-14 16:48 ` Paul E. McKenney [this message]
2009-04-17 22:14 ` Andrew Morton
2009-04-23 13:32 ` Jan Blunck
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=20090414164839.GI6753@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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