linux-kernel - Re: [PATCH 3/3] gpio: shared: allow sharing a reset-gpios pin between reset-gpio and gpiolib

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: <CAMRc=MeUBhDqQWKqSbRP+bpBcc0Xptdgdj9CMfOzJmgqARJMDQ@mail.gmail.com>
Date: Thu, 8 Jan 2026 16:52:24 +0100
From: Bartosz Golaszewski <brgl@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>, Linus Walleij <linusw@...nel.org>, 
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Linus Walleij <linus.walleij@...aro.org>, Aishwarya.TCV@....com
Subject: Re: [PATCH 3/3] gpio: shared: allow sharing a reset-gpios pin between
 reset-gpio and gpiolib

On Thu, Jan 8, 2026 at 4:46 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Mon, Dec 22, 2025 at 11:01:28AM +0100, Bartosz Golaszewski wrote:
> > We currently support sharing GPIOs between multiple devices whose drivers
> > use either the GPIOLIB API *OR* the reset control API but not both at
> > the same time.
>
> We're seeing futher issues which bisect to this patch in today's
> next/pending-fixes on db845c:
>
> <1>[   18.348426] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008
>
> ...
>
> <4>[   18.799534] Call trace:
> <4>[   18.799536]  gpiod_direction_output_nonotify+0x14/0x194 (P)
> <4>[   18.799541]  gpiod_configure_flags+0xb0/0x364
> <4>[   18.799543]  gpiod_find_and_request+0x144/0x504
> <4>[   18.832617]  gpiod_get_index+0x58/0x90
> <4>[   18.836657]  devm_gpiod_get_index+0x20/0xb0
> <4>[   18.841139]  devm_gpiod_get_optional+0x18/0x34
> <4>[   18.845881]  lt9611_probe+0x130/0x488 [lontium_lt9611]
>
> Some prior instances were fixed by:
>
>    https://lore.kernel.org/all/20260106-gpio-shared-fixes-v2-0-c7091d2f7581@oss.qualcomm.com/
>
> but that's only in next/master, not next/pending-fixes, and in any case
> the issue also appears in next/master which should include them.
>

Does the following fix it by any chance?

https://lore.kernel.org/all/20260108102314.18816-1-bartosz.golaszewski@oss.qualcomm.com

Bart