linux-kernel - Re: [PATCH 6.13 000/138] 6.13.5-rc1 review

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: <CACMJSeuQkzvi5j975bbb6gF=+NMz0Aw-X5xLXR=8rMUjeQUoZg@mail.gmail.com>
Date: Mon, 24 Feb 2025 20:57:10 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org, 
	patches@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org, linux@...ck-us.net, 
	shuah@...nel.org, patches@...nelci.org, lkft-triage@...ts.linaro.org, 
	pavel@...x.de, jonathanh@...dia.com, f.fainelli@...il.com, 
	sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de, 
	conor@...nel.org, hargar@...rosoft.com, 
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH 6.13 000/138] 6.13.5-rc1 review

On Mon, 24 Feb 2025 at 20:52, Mark Brown <broonie@...nel.org> wrote:
>
> On Mon, Feb 24, 2025 at 03:33:50PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.13.5 release.
> > There are 138 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
>
> This and 6.12 are broken on several platforms by "gpiolib: check the
> return value of gpio_chip::get_direction()", as reported upstream
> several drivers break the expectations that this commit has.
> 96fa9ec477ff60bed87e1441fd43e003179f3253 "gpiolib: don't bail out if
> get_direction() fails in gpiochip_add_data()" was merged upstream which
> makes this non-fatal, but it's probably as well to just not backport
> this to stable at all.

Agreed, this can be dropped. It never worked before so it's not a
regression fix.

Bartosz