From: Boqun Feng <boqun.feng@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Gautham R Shenoy <ego@linux.vnet.ibm.com>,
Byungchul Park <byungchul.park@lge.com>,
Boqun Feng <boqun.feng@gmail.com>
Subject: [RFC tip/locking v2 07/13] lockdep: Support deadlock detection for recursive read in check_noncircular()
Date: Wed, 6 Sep 2017 16:28:18 +0800 [thread overview]
Message-ID: <20170906082824.16078-8-boqun.feng@gmail.com> (raw)
In-Reply-To: <20170906082824.16078-1-boqun.feng@gmail.com>
Currently, lockdep only has limit support for deadlock detection for
recursive read locks.
The basic idea of the detection is:
Since we make __bfs() able to traverse only the strong dependency paths,
so we report a circular deadlock if we could find a circle of a strong
dependency path.
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
---
kernel/locking/lockdep.c | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
index d9959f25247a..8a09b1a02342 100644
--- a/kernel/locking/lockdep.c
+++ b/kernel/locking/lockdep.c
@@ -1345,6 +1345,14 @@ static inline int hlock_equal(struct lock_list *entry, void *data)
(hlock->read == 2 || !entry->is_rr);
}
+static inline int hlock_conflict(struct lock_list *entry, void *data)
+{
+ struct held_lock *hlock = (struct held_lock *)data;
+
+ return hlock_class(hlock) == entry->class &&
+ (hlock->read != 2 || !entry->is_rr);
+}
+
static noinline int print_circular_bug(struct lock_list *this,
struct lock_list *target,
struct held_lock *check_src,
@@ -1459,18 +1467,18 @@ unsigned long lockdep_count_backward_deps(struct lock_class *class)
}
/*
- * Prove that the dependency graph starting at <entry> can not
+ * Prove that the dependency graph starting at <root> can not
* lead to <target>. Print an error and return BFS_RMATCH if it does.
*/
static noinline enum bfs_result
-check_noncircular(struct lock_list *root, struct lock_class *target,
+check_noncircular(struct lock_list *root, struct held_lock *target,
struct lock_list **target_entry)
{
enum bfs_result result;
debug_atomic_inc(nr_cyclic_checks);
- result = __bfs_forwards(root, target, class_equal, target_entry);
+ result = __bfs_forwards(root, target, hlock_conflict, target_entry);
return result;
}
--
2.14.1
next prev parent reply other threads:[~2017-09-06 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 8:28 [RFC tip/locking v2 00/13] lockdep: Support deadlock detection for recursive read locks Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 01/13] lockdep: Demagic the return value of BFS Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 02/13] lockdep: Make __bfs() visit every dependency rather than every class until a match Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 03/13] lockdep: Change the meanings of LOCK_{USED_IN, ENABLED}_*_{READ} Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 04/13] lockdep: Introduce lock_list::dep Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 05/13] lockdep: Extend __bfs() to work with multiple kinds of dependencies Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 06/13] lockdep: Adjust check_redundant() for recursive read change Boqun Feng
2017-09-06 8:28 ` Boqun Feng [this message]
2017-09-06 8:28 ` [RFC tip/locking v2 08/13] lockdep: Fix recursive read lock related safe->unsafe detection Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 09/13] lockdep: Add recursive read locks into dependency graph Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 10/13] lockdep/selftest: Add a R-L/L-W test case specific to chain cache behavior Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 11/13] lockdep: Take read/write status in consideration when generate chainkey Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 12/13] lockdep/selftest: Unleash irq_read_recursion2 and add more Boqun Feng
2017-09-06 8:28 ` [RFC tip/locking v2 13/13] lockdep/selftest: Add more recursive read related test cases Boqun Feng
2017-09-06 8:49 ` [RFC tip/locking v2 00/13] lockdep: Support deadlock detection for recursive read locks Boqun Feng
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=20170906082824.16078-8-boqun.feng@gmail.com \
--to=boqun.feng@gmail.com \
--cc=byungchul.park@lge.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®