From: Davidlohr Bueso <dave@stgolabs.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: David Howells <dhowells@redhat.com>,
linux-afs@lists.infradead.org, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] rxrpc: struct mutex cannot be used for rxrpc_call::user_mutex
Date: Thu, 19 Dec 2019 09:44:17 -0800 [thread overview]
Message-ID: <20191219174417.jax2fy3fvrvrrpsq@linux-p48b> (raw)
In-Reply-To: <20191219090535.GV2844@hirez.programming.kicks-ass.net>
On Thu, 19 Dec 2019, Peter Zijlstra wrote:
>Automate what exactly?
What I meant was automating finding cases that are 'false positives' such
as rxrpc and kexec _before_ re-adding the warn.
Thanks,
Davidlohr
next prev parent reply other threads:[~2019-12-19 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 15:32 [PATCH] rxrpc: struct mutex cannot be used for rxrpc_call::user_mutex David Howells
2019-12-18 13:50 ` Peter Zijlstra
2019-12-18 19:08 ` Davidlohr Bueso
2019-12-18 20:28 ` Davidlohr Bueso
2019-12-19 9:05 ` Peter Zijlstra
2019-12-19 17:44 ` Davidlohr Bueso [this message]
2019-12-20 20:13 ` Peter Zijlstra
2019-12-18 20:39 ` Peter Zijlstra
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=20191219174417.jax2fy3fvrvrrpsq@linux-p48b \
--to=dave@stgolabs.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).