linux-kernel - Re: [PATCH 5.15 00/57] 5.15.155-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: <2024041402-impeach-charting-60f5@gregkh>
Date: Sun, 14 Apr 2024 08:13:32 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>,
	linux-stable <stable@...r.kernel.org>,
	"patches@...ts.linux.dev" <patches@...ts.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Guenter Roeck <linux@...ck-us.net>,
	"shuah@...nel.org" <shuah@...nel.org>,
	"patches@...nelci.org" <patches@...nelci.org>,
	"lkft-triage@...ts.linaro.org" <lkft-triage@...ts.linaro.org>,
	"pavel@...x.de" <pavel@...x.de>,
	"jonathanh@...dia.com" <jonathanh@...dia.com>,
	"f.fainelli@...il.com" <f.fainelli@...il.com>,
	"sudipm.mukherjee@...il.com" <sudipm.mukherjee@...il.com>,
	"srw@...dewatkins.net" <srw@...dewatkins.net>,
	"rwarsow@....de" <rwarsow@....de>,
	"conor@...nel.org" <conor@...nel.org>,
	"allen.lkml@...il.com" <allen.lkml@...il.com>,
	"broonie@...nel.org" <broonie@...nel.org>,
	Calum Mackay <calum.mackay@...cle.com>,
	Vegard Nossum <vegard.nossum@...cle.com>,
	Darren Kenny <darren.kenny@...cle.com>,
	Ramanan Govindarajan <ramanan.govindarajan@...cle.com>,
	Linux NFS Mailing List <linux-nfs@...r.kernel.org>
Subject: Re: [PATCH 5.15 00/57] 5.15.155-rc1 review

On Sat, Apr 13, 2024 at 11:56:15AM -0400, Chuck Lever wrote:
> On Sat, Apr 13, 2024 at 03:04:19AM +0530, Harshit Mogalapalli wrote:
> > Hi Chuck and Greg,
> > 
> > On 13/04/24 01:53, Chuck Lever wrote:
> > > On Sat, Apr 13, 2024 at 01:41:52AM +0530, Harshit Mogalapalli wrote:
> > > > # first bad commit: [2267b2e84593bd3d61a1188e68fba06307fa9dab] lockd:
> > > > introduce safe async lock op
> > > > 
> > > > 
> > > > Hope the above might help.
> > > 
> > > Nice work. Thanks!
> > > 
> > > 
> > > > I didnot test the revert of culprit commit on top of 5.15.154 yet.
> > > 
> > > Please try reverting that one -- it's very close to the top so one
> > > or two others might need to be pulled off as well.
> > > 
> > 
> > I have reverted the bad commit: 2267b2e84593 ("lockd: introduce safe async
> > lock op") and the test passes.
> > 
> > Note: Its reverts cleanly on 5.15.154
> 
> Harshit also informs me that "lockd: introduce safe async lock op"
> is not applied to v6.1, so it's not likely necessary to include here
> and can be safely reverted from v5.15.y.

Chuck, can you send a series of reverts for what needs to be done here
as these were your original backports?

thanks,

greg k-h