From: Peter Zijlstra <peterz@infradead.org>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, john.johansen@canonical.com,
paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] security/apparmor: Replace homebrew use of write_can_lock with lockdep
Date: Tue, 3 Oct 2017 17:07:09 +0200 [thread overview]
Message-ID: <20171003150709.53fz7daydyomfuly@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1507041166-10618-1-git-send-email-will.deacon@arm.com>
On Tue, Oct 03, 2017 at 03:32:45PM +0100, Will Deacon wrote:
> The lockdep subsystem provides a robust way to assert that a lock is
> held, so use that instead of write_can_lock, which can give incorrect
> results for qrwlocks.
>
> Cc: John Johansen <john.johansen@canonical.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
Thanks Will, good to be able to finally remove that API.
next prev parent reply other threads:[~2017-10-03 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 14:32 Will Deacon
2017-10-03 14:32 ` [PATCH 2/2] locking: Remove {read,write}_can_lock Will Deacon
2017-10-03 15:07 ` Peter Zijlstra [this message]
2017-10-03 16:58 ` [PATCH 1/2] security/apparmor: Replace homebrew use of write_can_lock with lockdep Will Deacon
2017-10-03 15:33 ` John Johansen
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=20171003150709.53fz7daydyomfuly@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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®