From: Derek Basehore <dbasehore@chromium.org>
To: peterz@infradead.org
Cc: mingo@redhat.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org,
Derek Basehore <dbasehore@chromium.org>
Subject: RFC [PATCH 0/1] Fix lockdep false positive
Date: Tue, 11 Dec 2018 18:25:05 -0800 [thread overview]
Message-ID: <20181212022506.171936-1-dbasehore@chromium.org> (raw)
I'm not sure if I'm breaking any detection with this patch since I
haven't looked at that lockdep code before. I do know that the unlock
order for locks with a nest lock should not matter, though.
Specifically, you should be able to unlock the nest lock followed by
all the locks nested underneath it.
Derek Basehore (1):
locking/lockdep: Fix nest lock warning on unlock
kernel/locking/lockdep.c | 27 +++++++++++++--------------
1 file changed, 13 insertions(+), 14 deletions(-)
--
2.20.0.rc2.403.gdbc3b29805-goog
next reply other threads:[~2018-12-12 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 2:25 Derek Basehore [this message]
2018-12-12 2:25 ` RFC [PATCH 1/1] locking/lockdep: Fix nest lock warning on unlock Derek Basehore
2018-12-12 9:09 ` Peter Zijlstra
2018-12-12 11:42 ` dbasehore .
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=20181212022506.171936-1-dbasehore@chromium.org \
--to=dbasehore@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.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®