linux-kernel - Re: [PATCH v2] gpio: shared: fix a deadlock

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] [day] [month] [year] [list]

Message-ID: <176431975833.13482.3073514830553688627.b4-ty@linaro.org>
Date: Fri, 28 Nov 2025 09:49:20 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...nel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
	Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	linux-arm-msm@...r.kernel.org,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] gpio: shared: fix a deadlock

From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>


On Fri, 28 Nov 2025 09:40:11 +0100, Bartosz Golaszewski wrote:
> It's possible that the auxiliary proxy device we add when setting up the
> GPIO controller exposing shared pins, will get matched and probed
> immediately. The gpio-proxy-driver will then retrieve the shared
> descriptor structure. That will cause a recursive mutex locking and
> a deadlock because we're already holding the gpio_shared_lock in
> gpio_device_setup_shared() and try to take it again in
> devm_gpiod_shared_get() like this:
> 
> [...]

Applied, thanks!

[1/1] gpio: shared: fix a deadlock
      https://git.kernel.org/brgl/linux/c/54a2df5afa2382d6fd1168a3caf151f50c68dfea

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