linux-kernel - Re: [PATCH v5.10 0/2] Fix for CVE-2024-36901

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>] [day] [month] [year] [list]

Message-ID: <2024071323-disarray-moody-1e0b@gregkh>
Date: Sat, 13 Jul 2024 13:05:52 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Ashwin Kamat <ashwin.kamat@...adcom.com>
Cc: linux-kernel@...r.kernel.org, davem@...emloft.net,
	yoshfuji@...ux-ipv6.org, dsahern@...nel.org, kuba@...nel.org,
	netdev@...r.kernel.org, ajay.kaher@...adcom.com,
	vasavi.sirnapalli@...adcom.com, tapas.kundu@...adcom.com
Subject: Re: [PATCH v5.10 0/2] Fix for CVE-2024-36901

On Sat, Jul 13, 2024 at 03:16:15PM +0530, Ashwin Kamat wrote:
> Hi Greg,
> The patches get applied to 5.10 stable branch with an offset [i.e Hunk #1
> succeeded at 240 (offset 19 lines).]
> To avoid that I sent separate patches to 5.10 and 5.15. Apart from that
> there is no other difference.

That's not what I asked, I asked:

> > Any reason you didn't actually cc: the stable@...r.kernel.org address
> > for these so we know to pick them up?

That is a requirement to get a patch merged into a stable release,
right?

thanks,

greg k-h