linux-kernel - Re: [PATCH 4.19 000/175] 4.19.312-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] [day] [month] [year] [list]

Date: Tue, 30 Apr 2024 14:30:10 +0800
From: Genjian <zhanggenjian@....com>
To: gregkh@...uxfoundation.org
Cc: akpm@...ux-foundation.org,
	allen.lkml@...il.com,
	broonie@...nel.org,
	christophe.jaillet@...adoo.fr,
	conor@...nel.org,
	f.fainelli@...il.com,
	jonathanh@...dia.com,
	linux-kernel@...r.kernel.org,
	linux@...ck-us.net,
	lkft-triage@...ts.linaro.org,
	maco@...roid.com,
	patches@...nelci.org,
	patches@...ts.linux.dev,
	pavel@...x.de,
	rwarsow@....de,
	sean.anderson@...ux.dev,
	shuah@...nel.org,
	srw@...dewatkins.net,
	stable@...r.kernel.org,
	sudipm.mukherjee@...il.com,
	tglx@...utronix.de,
	torvalds@...ux-foundation.org,
	zhanggenjian@...inos.cn
Subject: Re: [PATCH 4.19 000/175] 4.19.312-rc1 review

> On Fri, Apr 12, 2024 at 09:46:46PM +0200, Pavel Machek wrote:
> > Hi!
> > 
> > > This is the start of the stable review cycle for the 4.19.312 release.
> > > There are 175 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.
> > 
> > > Martijn Coenen <maco@...roid.com>
> > >     loop: Remove sector_t truncation checks
> > 
> > AFAICT, in 4.19, sector_t is not guaranteed to be u64, see
> > include/linux/types.h. So we can't take this.
> 
> It's more helpful if you cc: the people on the commit that you are
> asking about, so that they can explain why they asked for it, or did the
> backport.
> 
> Genjian, any thoughts about this one?
> 
> thanks,
> 
> greg k-h

This one was aimed at resolving merge conflicts with subsequent patches and had no other reason. Indeed, this patch is not suitable for 4.19. I'm sorry for the omission.

thanks,

Genjian