linux-kernel - [PATCH v1 0/2] gpiolib: legacy: Allow *gpio_request

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

Message-ID: <20251112093608.1481030-1-andriy.shevchenko@linux.intel.com>
Date: Wed, 12 Nov 2025 10:32:00 +0100
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org
Cc: Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>
Subject: [PATCH v1 0/2] gpiolib: legacy: Allow *gpio_request_one() to die independently

Allow *gpio_request_one() to die independently and make sure
the gpio_request_one() gone first (before gpio_request() removal).
Currently the devm_gpio_request_one() depends on gpio_request_one().
Open code the latter in the former to break the dependency. Also
convert the latter to use legacy APIs, so we can kill it first
as it's not only the logical move, but an easier task due to less
amount of the leftover users in the kernel.

Besides that, we gain a few LoCs with this small refactoring, which
I consider a positive change alone.

Andy Shevchenko (2):
  gpiolib: legacy: Make sure we kill gpio_request_one() first
  gpiolib: legacy: Allow to kill devm_gpio_request_one() independently

 drivers/gpio/gpiolib-legacy.c | 44 +++++++++++++----------------------
 1 file changed, 16 insertions(+), 28 deletions(-)

-- 
2.50.1