linux-kernel - Re: [PATCH 5.10.y] fs/jfs: cast inactags to s64 to prevent potential overflow

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

Message-ID: <tx4mjsvkleki6butsmbh533y6w55rt44zaorh6auhjyfgzunj3@oaiwslri6x5h>
Date: Wed, 19 Feb 2025 14:37:11 +0300
From: Fedor Pchelkin <pchelkin@...ras.ru>
To: Rand Deeb <rand.sec96@...il.com>
Cc: Dave Kleikamp <shaggy@...nel.org>, 
	jfs-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org, 
	voskresenski.stanislav@...fident.ru, Rand Deeb <deeb.rand@...fident.ru>, lvc-project@...uxtesting.org
Subject: Re: [PATCH 5.10.y] fs/jfs: cast inactags to s64 to prevent potential
 overflow

On Wed, 19. Feb 14:10, Rand Deeb wrote:
> I focused on 5.10 and added it to the subject to avoid confusion,
> since files differ across versions. But yes, all versions have the issue.
> In one of my past patches, maintainers couldn't apply it due to kernel
> version differences, which led to confusion. So I thought specifying
> the version upfront would help. My bad, I should have noted it after
> the commit message instead.

The officially supported stable kernel branches can take the patch if it
or its equivalent is already present in the mainline.
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

> 
> I'll take this into account in future patches. Should I send another
> patch specifically for the mainline version now?

Yes. And not specifically, but deliberately (it's a requirement). The
existing problems should be fixed there at first.