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: <2024051744-refinery-galore-0089@gregkh>
Date: Fri, 17 May 2024 11:26:25 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Pavel Machek <pavel@...x.de>
Cc: 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,
	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 5.10 000/111] 5.10.217-rc1 review

On Fri, May 17, 2024 at 11:22:37AM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 16, 2024 at 02:38:48PM +0200, Pavel Machek wrote:
> > Hi!
> > 
> > > This is the start of the stable review cycle for the 5.10.217 release.
> > > There are 111 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.
> > 
> > 
> > > Stephen Boyd <sboyd@...nel.org>
> > >     clk: Don't hold prepare_lock when calling kref_put()
> > 
> > Stephen said in a message that this depends on other patches,
> > including 9d1e795f754d clk: Get runtime PM before walking tree for
> > clk_summary. But we don't seem to have that one. Can you double-check?
> > 
> > (
> > Date: Tue, 23 Apr 2024 12:24:51 -0700
> > Subject: Re: [PATCH AUTOSEL 5.4 6/8] clk: Don't hold prepare_lock when calling kref_put()
> > )
> 
> Ugh, please use lore links when referring to other threads so that we
> don't have to figure it out on our own...
> 
> Anyway, that one commit seems missing, I'll look into it.

And I know you mean well, but if you had looked at it, you would have
seen that that commit isn't relevant at all to this kernel branch, which
is why it is not there.

Please be more careful with your reviews.

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ