linux-kernel - Re: [PATCH 6.6 000/741] 6.6.33-rc2 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]

Date: Tue, 18 Jun 2024 15:18:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, 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,
	allen.lkml@...il.com, broonie@...nel.org
Subject: Re: [PATCH 6.6 000/741] 6.6.33-rc2 review

On Mon, Jun 17, 2024 at 10:38:29AM -0700, Guenter Roeck wrote:
> Hi,
> 
> On 6/9/24 04:41, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.6.33 release.
> > There are 741 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.
> > 
> > Responses should be made by Tue, 11 Jun 2024 11:36:08 +0000.
> > Anything received after that time might be too late.
> > 
> [ ... ]
> > 
> > Duanqiang Wen <duanqiangwen@...-swift.com>
> >      Revert "net: txgbe: fix clk_name exceed MAX_DEV_ID limits"
> > 
> 
> This patch, in its commit message, explicitly states:
> 
>   This reverts commit e30cef001da259e8df354b813015d0e5acc08740.
>   commit 99f4570cfba1 ("clkdev: Update clkdev id usage to allow
>   for longer names") can fix clk_name exceed MAX_DEV_ID limits,
>   so this commit is meaningless.
> 
> However, commit 99f4570cfba1 has not been applied to v6.6.y,
> meaning the revert may impact the affected driver under some
> circumstances.

Ah, that was tricky, thanks, I've queued up 99f4570cfba1 now.

greg k-h