From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arne Jansen <lists@die-jansens.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
efault@gmx.de, npiggin@kernel.dk, akpm@linux-foundation.org,
frank.rowand@am.sony.com, tglx <tglx@linutronix.de>
Subject: [PATCH] lockdep: Fix lock_is_held on recursion
Date: Tue, 07 Jun 2011 00:19:19 +0200 [thread overview]
Message-ID: <1307398759.2497.966.camel@laptop> (raw)
Subject: lockdep: Fix lock_is_held on recursion
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date: Mon Jun 06 12:32:43 CEST 2011
The main lock_is_held() user is lockdep_assert_held(), avoid false
assertions in lockdep_off() sections by unconditionally reporting the
lock is taken.
[ the reason this is important is a lockdep_assert_held() in ttwu()
which triggers a warning under lockdep_off() as in printk() which
can trigger another wakeup and lock up due to spinlock recursion ]
Reported-and-tested-by: Arne Jansen <lists@die-jansens.de>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
Index: linux-2.6/kernel/lockdep.c
===================================================================
--- linux-2.6.orig/kernel/lockdep.c
+++ linux-2.6/kernel/lockdep.c
@@ -3426,7 +3426,7 @@ int lock_is_held(struct lockdep_map *loc
int ret = 0;
if (unlikely(current->lockdep_recursion))
- return ret;
+ return 1; /* avoid false negative lockdep_assert_held */
raw_local_irq_save(flags);
check_flags(flags);
next reply other threads:[~2011-06-06 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 22:19 Peter Zijlstra [this message]
2011-06-07 12:02 ` [tip:sched/urgent] lockdep: Fix lock_is_held() on recursion tip-bot for Peter Zijlstra
2011-06-07 12:39 ` Peter Zijlstra
2011-06-07 18:06 ` Ingo Molnar
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=1307398759.2497.966.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=frank.rowand@am.sony.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@die-jansens.de \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=npiggin@kernel.dk \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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