From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hillf Danton <hdanton@sina.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Converting dev->mutex into dev->spinlock ?
Date: Mon, 6 Feb 2023 07:48:03 +0100 [thread overview]
Message-ID: <Y+Cio48RvJe9Y2cv@kroah.com> (raw)
In-Reply-To: <20230206064305.1838-1-hdanton@sina.com>
On Mon, Feb 06, 2023 at 02:43:05PM +0800, Hillf Danton wrote:
> On Mon, 6 Feb 2023 06:17:03 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > On Mon, Feb 06, 2023 at 10:56:29AM +0800, Hillf Danton wrote:
> > > On Sun, 5 Feb 2023 11:46:06 -0500 Alan Stern <stern@rowland.harvard.edu>
> > > >
> > > > And by the way, by disabling lockdep validation I am declaraing that
> > > > enabling it would cause an overwhelming number of false positives,
> > >
> > > Could you share 5 false positives you see upstream to help understand how
> > > it is useless?
> >
> > Please see this other email in this thread:
> > https://lore.kernel.org/r/Y98FLlr7jkiFlV0k@rowland.harvard.edu
>
> What lockdep warnings? Specific examples, please.
Remove the one line of code, as per the patch in this thread, and boot
with lockdep enabled and see what happens if you wish to see them
yourself.
thanks,
greg k-h
prev parent reply other threads:[~2023-02-06 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <28a82f50-39d5-a45f-7c7a-57a66cec0741@I-love.SAKURA.ne.jp>
[not found] ` <Y951z0Au9MlP1GxX@rowland.harvard.edu>
[not found] ` <e89ad942-cab6-fad1-1cc2-98885d829ea7@I-love.SAKURA.ne.jp>
[not found] ` <Y958hOvtqq7Uiu0G@rowland.harvard.edu>
2023-02-05 0:21 ` Hillf Danton
[not found] ` <Y95h7Vop9t5Li0HD@kroah.com>
[not found] ` <a236ab6b-d38c-3974-d4cb-5e92d0877abc@I-love.SAKURA.ne.jp>
[not found] ` <Y957GSFVAQz8v3Xo@rowland.harvard.edu>
[not found] ` <cf56ebc3-187a-6ee4-26bc-2d180272b5cf@I-love.SAKURA.ne.jp>
[not found] ` <Y96HiYcreb8jZIHi@rowland.harvard.edu>
[not found] ` <917e1e3b-094f-e594-c1a2-8b97fb5195fd@I-love.SAKURA.ne.jp>
[not found] ` <Y965qEg0Re2QoQ7Q@rowland.harvard.edu>
[not found] ` <c7fb01a9-3e12-77ed-5c4c-db7deb64dc73@I-love.SAKURA.ne.jp>
[not found] ` <Y9/dTp/hQ5btWTEH@rowland.harvard.edu>
2023-02-06 2:56 ` Hillf Danton
2023-02-06 4:44 ` Matthew Wilcox
2023-02-06 5:17 ` Greg Kroah-Hartman
2023-02-06 6:43 ` Hillf Danton
2023-02-06 6:48 ` Greg Kroah-Hartman [this message]
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=Y+Cio48RvJe9Y2cv@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rafael@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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