From: Peter Zijlstra <peterz@infradead.org>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
SElinux list <selinux@vger.kernel.org>
Subject: Re: Semantics vs. usage of mutex_is_locked()
Date: Mon, 7 Feb 2022 16:47:39 +0100 [thread overview]
Message-ID: <20220207154739.GH23216@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFqZXNt0Xp1j7+hTrV9XZ936Yz+H8Le0pqazhLr3drO0tEzB2w@mail.gmail.com>
On Mon, Feb 07, 2022 at 04:15:27PM +0100, Ondrej Mosnacek wrote:
> Also, any opinions on the name of the new helper? Perhaps
> mutex_is_held()? Or mutex_is_locked_by_current()?
lockdep_assert_held*() and friends work on mutexes just fine.
next prev parent reply other threads:[~2022-02-07 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 15:15 Semantics vs. usage of mutex_is_locked() Ondrej Mosnacek
2022-02-07 15:47 ` Peter Zijlstra [this message]
2022-02-07 16:52 ` Ondrej Mosnacek
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=20220207154739.GH23216@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=will@kernel.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