[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y+hW74TAVzCpSv7c@rowland.harvard.edu>
Date: Sat, 11 Feb 2023 22:03:11 -0500
From: Alan Stern <stern@...land.harvard.edu>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: Kent Overstreet <kent.overstreet@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Coly Li <colyli@...e.de>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
syzkaller <syzkaller@...glegroups.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Boqun Feng <boqun.feng@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
Hillf Danton <hdanton@...a.com>
Subject: Re: [PATCH RFC] drivers/core: Replace lockdep_set_novalidate_class()
with unique class keys
On Sat, Feb 11, 2023 at 09:46:42PM -0500, Kent Overstreet wrote:
> On Sat, Feb 11, 2023 at 09:40:58PM -0500, Alan Stern wrote:
> > Or maybe you're referring to what this patch does? It does indeed
> > create a bunch of dynamic classes -- one for each struct device. The
> > ordering rules derived by lockdep will be somewhat arbitrary, as you
> > say. But some of them certainly will be related to the structure of the
> > source code.
>
> I could be :) I haven't been able to find the patch in question - have a
> link?
It was earlier in this email thread. Here's a link:
https://lore.kernel.org/r/Y+gLd78vChQERZ6A@rowland.harvard.edu/
> If you're talking about making lock_class_key dynamic, I think I stand
> by what I said though - OTOH, if all you're doing is lifting that to the
> caller of the device object init function, so it'll still be a static
> object in the driver, that would be totally fine.
The patch does the first, not the second. Feel free to object some
more... :-)
Alan Stern
> I probably should've found the patch before commenting :)
Powered by blists - more mailing lists