From: Davidlohr Bueso <dave@stgolabs.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH -tip] locking/mutex: Complain upon api misuse wrt interrupt context
Date: Fri, 25 Oct 2019 10:27:49 -0700 [thread overview]
Message-ID: <20191025172749.ugi3hcehqbldit7i@linux-p48b> (raw)
In-Reply-To: <20191025081037.GF4131@hirez.programming.kicks-ass.net>
On Fri, 25 Oct 2019, Peter Zijlstra wrote:
>No real objection, but should not lockdep already complain about this?
>__mutex_unlock_slowpath() takes ->wait_lock irq-unsafe, so then using it
>from an IRQ should generate an insta IRQ inversion report.
But we still have the unlock fastpath and the trylock scenarios which
don't take locks.
Thanks,
davidlohr
next prev parent reply other threads:[~2019-10-25 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 3:36 [PATCH -tip] locking/mutex: Complain upon api misuse wrt interrupt context Davidlohr Bueso
2019-10-25 8:10 ` Peter Zijlstra
2019-10-25 17:27 ` Davidlohr Bueso [this message]
2019-10-30 10:03 ` [tip: locking/core] locking/mutex: Complain upon mutex API misuse in IRQ contexts tip-bot2 for Davidlohr Bueso
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=20191025172749.ugi3hcehqbldit7i@linux-p48b \
--to=dave@stgolabs.net \
--cc=dbueso@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).