From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Linus Walleij <linusw@kernel.org>,
driver-core@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
tzungbi@kernel.org
Subject: [PATCH v12 0/3] drivers/base: Introduce revocable
Date: Tue, 8 Sep 2026 21:42:20 +0800 [thread overview]
Message-ID: <20260908134223.13638-1-tzungbi@kernel.org> (raw)
This series introduces the "revocable" mechanism, a synchronization
primitive designed to prevent Use-After-Free errors.
- Patch 1 introduces the revocable which is an implementation of ideas
from the talk [1][2].
- Patch 2 adds KUnit test cases.
- Patch 3 transitions the UAF prevention logic within the GPIO core
(gpiolib) to use the "revocable" mechanism.
The existing code aims to prevent UAF issues when the underlying GPIO
chip is removed. The patch replaces that custom logic with the
generic "revocable" API, which is designed to handle such lifecycle
dependencies. There should be no changes in behavior.
Since v9, there are two ways to manage the resource provider handle.
- Embedded allocation: patch 3 is the user.
- Dynamic allocation: no user yet.
[1] https://lpc.events/event/17/contributions/1627/
[2] https://lpc.events/event/19/contributions/2262/
---
v12:
- Rebase onto next-20260907.
- Drop patch 4 and 5.
v11: https://lore.kernel.org/all/20260513091043.6766-1-tzungbi@kernel.org
- Rebase onto v7.1-rc3.
- Squash patches 4 to 7 into patch 3. A single patch for GPIO.
v10: https://lore.kernel.org/all/20260508105448.31799-1-tzungbi@kernel.org
- Unify handling of embedded and dynamic allocation.
v9: https://lore.kernel.org/all/20260427135841.96266-1-tzungbi@kernel.org
- Rebase onto v7.1-rc1.
- Remove the selftests patch as it makes less sense to test revocable
APIs via kselftests.
- Merge patches 7 to 11 from
https://lore.kernel.org/all/20260213092958.864411-1-tzungbi@kernel.org
into the series.
- Merge patch from
https://lore.kernel.org/all/20250923075302.591026-5-tzungbi@kernel.org
- Merge patch from
https://lore.kernel.org/all/20250912081718.3827390-6-tzungbi@kernel.org
v8: https://lore.kernel.org/all/20260213092307.858908-1-tzungbi@kernel.org
- Rework on the revocable APIs. See changelog in [PATCH v8 1/3] for details.
v7: https://lore.kernel.org/all/20260116080235.350305-1-tzungbi@kernel.org
- Rebase onto next-20260115.
v6: https://lore.kernel.org/all/20251106152330.11733-1-tzungbi@kernel.org
- Rebase onto next-20251106.
- Separate revocable core and use cases.
v5: https://lore.kernel.org/all/20251016054204.1523139-1-tzungbi@kernel.org
- Rebase onto next-20251015.
- Add more context about the PoC.
- Support multiple revocable providers in the PoC.
v4: https://lore.kernel.org/all/20250923075302.591026-1-tzungbi@kernel.org
- Rebase onto next-20250922.
- Remove the 5th patch from v3.
- Add fops replacement PoC in 5th - 7th patches.
v3: https://lore.kernel.org/all/20250912081718.3827390-1-tzungbi@kernel.org
- Rebase onto https://lore.kernel.org/all/20250828083601.856083-1-tzungbi@kernel.org
and next-20250912.
- The 4th patch changed accordingly.
v2: https://lore.kernel.org/all/20250820081645.847919-1-tzungbi@kernel.org
- Rename "ref_proxy" -> "revocable".
- Add test cases in Kunit and selftest.
v1: https://lore.kernel.org/all/20250814091020.1302888-1-tzungbi@kernel.org
Tzung-Bi Shih (3):
revocable: Revocable resource management
revocable: Add KUnit test cases
gpio: Leverage revocable for accessing struct gpio_chip
.../driver-api/driver-model/index.rst | 1 +
.../driver-api/driver-model/revocable.rst | 384 +++++++++++++++++
MAINTAINERS | 11 +
drivers/base/Makefile | 2 +-
drivers/base/revocable.c | 267 ++++++++++++
drivers/base/test/Kconfig | 5 +
drivers/base/test/Makefile | 4 +
drivers/base/test/revocable-test.c | 406 ++++++++++++++++++
drivers/gpio/gpiolib-cdev.c | 77 ++--
drivers/gpio/gpiolib-sysfs.c | 31 +-
drivers/gpio/gpiolib.c | 259 +++++------
drivers/gpio/gpiolib.h | 28 +-
include/linux/revocable.h | 204 +++++++++
13 files changed, 1438 insertions(+), 241 deletions(-)
create mode 100644 Documentation/driver-api/driver-model/revocable.rst
create mode 100644 drivers/base/revocable.c
create mode 100644 drivers/base/test/revocable-test.c
create mode 100644 include/linux/revocable.h
--
2.53.0
next reply other threads:[~2026-09-08 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 13:42 Tzung-Bi Shih [this message]
2026-09-08 13:42 ` [PATCH v12 1/3] revocable: Revocable resource management Tzung-Bi Shih
2026-09-08 13:42 ` [PATCH v12 2/3] revocable: Add KUnit test cases Tzung-Bi Shih
2026-09-08 13:42 ` [PATCH v12 3/3] gpio: Leverage revocable for accessing struct gpio_chip Tzung-Bi Shih
2026-09-10 7:32 ` Bartosz Golaszewski
2026-09-12 12:38 ` Tzung-Bi Shih
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=20260908134223.13638-1-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=brgl@kernel.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®