From: Jan Blunck <jblunck@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: npiggin@suse.de, paulmck@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atomic: Only take lock when the counter drops to zero on UP as well
Date: Thu, 23 Apr 2009 15:32:11 +0200 [thread overview]
Message-ID: <20090423133211.GT11220@bolzano.suse.de> (raw)
In-Reply-To: <20090417151405.3ca49c39.akpm@linux-foundation.org>
On Fri, Apr 17, Andrew Morton wrote:
> On Fri, 10 Apr 2009 18:13:57 +0200
> Jan Blunck <jblunck@suse.de> 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.
> >
>
> It can't deadlock, because spin_lock() doesn't do anything on
> CONFIG_SMP=n.
>
> You might get lockdep whines on CONFIG_SMP=n, but they'd be false
> positives because lockdep doesn't know that we generate additional code
> for SMP builds.
Sorry, you are right. spin_lock() isn't the problem here. _raw_spin_lock()
calls into __spin_lock_debug():
static void __spin_lock_debug(spinlock_t *lock)
{
u64 i;
u64 loops = loops_per_jiffy * HZ;
int print_once = 1;
for (;;) {
for (i = 0; i < loops; i++) {
if (__raw_spin_trylock(&lock->raw_lock))
return;
__delay(1);
}
/* lockup suspected: */
if (print_once) {
print_once = 0;
printk(KERN_EMERG "BUG: spinlock lockup on CPU#%d, "
"%s/%d, %p\n",
raw_smp_processor_id(), current->comm,
task_pid_nr(current), lock);
dump_stack();
#ifdef CONFIG_SMP
trigger_all_cpu_backtrace();
#endif
}
}
}
This is an endless loop in this cases since the lock is already held and
therefore __raw_spin_trylock() never succeeds.
> > ---
> > 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))
>
> The patch looks reasonable from a cleanup/consistency POV, but the
> analysis and changelog need a bit of help, methinks.
>
Sorry, I'll come up with a more verbose description of the root cause of how
this locks up.
Cheers,
Jan
prev parent reply other threads:[~2009-04-23 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 16:13 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
2009-04-17 22:14 ` Andrew Morton
2009-04-23 13:32 ` Jan Blunck [this message]
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=20090423133211.GT11220@bolzano.suse.de \
--to=jblunck@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=paulmck@us.ibm.com \
/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
all inboxes | Powered by JetHome®