Re: [PATCH 0/2] gpio: core: fix const-correctness and remove UAF FIXMEs

[Bartosz Golaszewski]

On Sun, 24 May 2026 18:27:06 +0200, Marco Scardovi (scardracs) wrote:
> This series addresses legacy "FIXME Cannot use gpio_chip_guard due to
> const desc" comments and open-coded SRCU locks scattered throughout the
> gpiolib core and backend lookup paths.
> 
> I am aware of the ongoing work to replace the gpio_chip_guard architecture
> entirely (see the "revocable objects" patchset discussion at
> https://lore.kernel.org/linux-gpio/20260513091043.6766-1-tzungbi@xxxxxxxxxx/).
> While that broader refactoring is being iterated upon, this patch series
> provides a simple, completely type-safe fix utilizing the existing SRCU
> guard infrastructure. It can be merged today to eliminate the FIXMEs
> without conflicting conceptually with future revocable objects.
> 
> [...]

Applied, thanks!

[1/2] gpio: core: fix const-correctness of gpio_chip_guard
      https://git.kernel.org/brgl/c/aa7e8b7ef03151305a387654280306684687ade9
[2/2] gpio: remove obsolete UAF FIXMEs from lookup paths
      https://git.kernel.org/brgl/c/07c44ee9fdf196dcec14675c793e3139ec8a15b5

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxxxxxxxx>