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/lockdep v3 09/14] lockdep: Add recursive read locks into dependency graph
Date: Tue, 26 Sep 2017 06:18:43 +0800 [thread overview]
Message-ID: <20170925221848.6646-10-boqun.feng@gmail.com> (raw)
In-Reply-To: <20170925221848.6646-1-boqun.feng@gmail.com>
Since we have all the fundamental to handle recursive read locks, we now
add them into the dependency graph.
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
---
kernel/locking/lockdep.c | 16 +++-------------
1 file changed, 3 insertions(+), 13 deletions(-)
diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
index c29b058c37b3..cae595168970 100644
--- a/kernel/locking/lockdep.c
+++ b/kernel/locking/lockdep.c
@@ -2033,16 +2033,6 @@ check_prev_add(struct task_struct *curr, struct held_lock *prev,
if (!check_prev_add_irq(curr, prev, next))
return 0;
- /*
- * For recursive read-locks we do all the dependency checks,
- * but we dont store read-triggered dependencies (only
- * write-triggered dependencies). This ensures that only the
- * write-side dependencies matter, and that if for example a
- * write-lock never takes any other locks, then the reads are
- * equivalent to a NOP.
- */
- if (next->read == 2 || prev->read == 2)
- return 1;
/*
* Is the <prev> -> <next> dependency already present?
*
@@ -2164,7 +2154,7 @@ check_prevs_add(struct task_struct *curr, struct held_lock *next)
* Only non-recursive-read entries get new dependencies
* added:
*/
- if (hlock->read != 2 && hlock->check) {
+ if (hlock->check) {
int ret = check_prev_add(curr, hlock, next,
distance, &trace, save);
if (!ret)
@@ -4965,7 +4955,7 @@ static inline struct lock_class *xlock_class(struct cross_lock *xlock)
*/
static inline int depend_before(struct held_lock *hlock)
{
- return hlock->read != 2 && hlock->check && !hlock->trylock;
+ return hlock->check && !hlock->trylock;
}
/*
@@ -4973,7 +4963,7 @@ static inline int depend_before(struct held_lock *hlock)
*/
static inline int depend_after(struct held_lock *hlock)
{
- return hlock->read != 2 && hlock->check;
+ return hlock->check;
}
/*
--
2.14.1
next prev parent reply other threads:[~2017-09-25 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 22:18 [RFC tip/locking/lockdep v3 00/14] lockdep: Support deadlock detection for recursive read locks Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 01/14] lockdep: Demagic the return value of BFS Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 02/14] lockdep: Make __bfs() visit every dependency until a match Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 03/14] lockdep: Redefine LOCK_*_STATE* bits Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 04/14] lockdep: Introduce lock_list::dep Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 05/14] lockdep: Extend __bfs() to work with multiple kinds of dependencies Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 06/14] lockdep: Support deadlock detection for recursive read in check_noncircular() Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 07/14] lockdep: Adjust check_redundant() for recursive read change Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 08/14] lockdep: Fix recursive read lock related safe->unsafe detection Boqun Feng
2017-09-25 22:18 ` Boqun Feng [this message]
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 10/14] lockdep/selftest: Add a R-L/L-W test case specific to chain cache behavior Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 11/14] lockdep: Take read/write status in consideration when generate chainkey Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 12/14] lockdep/selftest: Unleash irq_read_recursion2 and add more Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 13/14] lockdep/selftest: Add more recursive read related test cases Boqun Feng
2017-09-25 22:18 ` [RFC tip/locking/lockdep v3 14/14] Revert "locking/lockdep/selftests: Fix mixed read-write ABBA tests" 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=20170925221848.6646-10-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®