From: Jason Gunthorpe <jgg@nvidia.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Danilo Krummrich <dakr@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Benson Leung <bleung@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
chrome-platform@lists.linux.dev, linux-kselftest@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
Dan Williams <dan.j.williams@intel.com>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v7 1/3] revocable: Revocable resource management
Date: Fri, 16 Jan 2026 14:24:31 -0400 [thread overview]
Message-ID: <20260116182431.GA1134360@nvidia.com> (raw)
In-Reply-To: <CAMRc=MfAZxzd2hjqgDsXBR+UxgkaEQX0vR5nNZ=a+5WccUb4GQ@mail.gmail.com>
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@kernel.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
next prev parent reply other threads:[~2026-01-16 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 8:02 [PATCH v7 0/3] drivers/base: Introduce revocable Tzung-Bi Shih
2026-01-16 8:02 ` [PATCH v7 1/3] revocable: Revocable resource management Tzung-Bi Shih
2026-01-16 15:19 ` Danilo Krummrich
2026-01-16 15:27 ` Bartosz Golaszewski
2026-01-16 15:35 ` Danilo Krummrich
2026-01-16 16:04 ` Laurent Pinchart
2026-01-16 16:41 ` Danilo Krummrich
2026-01-16 18:19 ` Bartosz Golaszewski
2026-01-16 18:24 ` Jason Gunthorpe [this message]
2026-01-16 18:31 ` Bartosz Golaszewski
2026-02-04 13:12 ` Bartosz Golaszewski
2026-01-16 8:02 ` [PATCH v7 2/3] revocable: Add Kunit test cases Tzung-Bi Shih
2026-01-16 8:02 ` [PATCH v7 3/3] selftests: revocable: Add kselftest cases Tzung-Bi Shih
2026-01-16 15:17 ` [PATCH v7 0/3] drivers/base: Introduce revocable Greg Kroah-Hartman
2026-01-16 16:04 ` Laurent Pinchart
2026-01-16 16:16 ` Danilo Krummrich
2026-01-16 16:52 ` Jason Gunthorpe
2026-01-16 17:00 ` Danilo Krummrich
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=20260116182431.GA1134360@nvidia.com \
--to=jgg@nvidia.com \
--cc=bleung@chromium.org \
--cc=brgl@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=shuah@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=tzungbi@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.