linux-kernel - Re: [PATCH v3 0/4] gpio: Hide and obey valid

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: <174118182949.69056.4837861377864682454.b4-ty@linaro.org>
Date: Wed,  5 Mar 2025 14:37:15 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Matti Vaittinen <mazziesaccount@...il.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Biju Das <biju.das.jz@...renesas.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [PATCH v3 0/4] gpio: Hide and obey valid_mask

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


On Wed, 05 Mar 2025 15:11:59 +0200, Matti Vaittinen wrote:
> GPIO controllers may have some pins which can be excluded from the GPIO
> usage on certain hardware configurations. The valid_mask member of the
> struct gpio_chip has been used to denote usable pins if some pins should
> be excluded.
> 
> The GPIO request should fail for GPIOs which are masked. Under certain
> conditions this was only done when GPIO chip provided the 'request'
> callback. We fix this to be always done.
> 
> [...]

Applied, thanks!

[1/4] gpio: Respect valid_mask when requesting GPIOs
      commit: a501624864f3fd9ab785f1f674f48dca535b198c
[2/4] gpio: Add a valid_mask getter
      commit: f636d4f60ac477187a466a573f947731fa762059
[3/4] gpio: gpio-rcar: Drop direct use of valid_mask
      commit: 43b665c961a6468fa8416805ef71daa5e7a152e7
[4/4] gpio: Hide valid_mask from direct assignments
      commit: 8015443e24e76fac97268603e91c4793970ce657

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