linux-kernel - Re: [PATCH v7 1/3] revocable: Revocable resource management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260116182431.GA1134360@nvidia.com>
Date: Fri, 16 Jan 2026 14:24:31 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Bartosz Golaszewski <brgl@...nel.org>
Cc: Danilo Krummrich <dakr@...nel.org>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Tzung-Bi Shih <tzungbi@...nel.org>,
	Benson Leung <bleung@...omium.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J . Wysocki" <rafael@...nel.org>,
	Linus Walleij <linusw@...nel.org>, Jonathan Corbet <corbet@....net>,
	Shuah Khan <shuah@...nel.org>, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, chrome-platform@...ts.linux.dev,
	linux-kselftest@...r.kernel.org,
	Wolfram Sang <wsa+renesas@...g-engineering.com>,
	Simona Vetter <simona.vetter@...ll.ch>,
	Dan Williams <dan.j.williams@...el.com>, linux-gpio@...r.kernel.org
Subject: Re: [PATCH v7 1/3] revocable: Revocable resource management

On Fri, Jan 16, 2026 at 07:19:50PM +0100, Bartosz Golaszewski wrote:
> On Fri, Jan 16, 2026 at 5:41 PM Danilo Krummrich <dakr@...nel.org> wrote:
> >
> > On Fri Jan 16, 2026 at 5:04 PM CET, Laurent Pinchart wrote:
> > > Based on the discussions we had at LPC, the revocable resource management API
> > > is not the right solution to handle races between device removal and userspace
> > > access.
> >
> > Please see: https://lore.kernel.org/all/DFQ5D44A0348.PZJIGPL972N@kernel.org/
> >
> > > It is however a possibly useful tool for races between producers and consumers
> > > *inside the kernel*.
> >
> > Do you have an example for such a case?
> 
> Isn't the GPIO use-case - which the series on top of it addresses - one?
> 
> With fw_devlink=off it's quite easy to trigger all kinds of crashes
> with in-kernel users.

Does this series solve that? It looked to me like it just replaces the
existing SRCU with a wrapper?

Jason