linux-kernel - Re: [PATCH v2 1/3] mm/ksm: Fix incorrect KSM counter handling in mm

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: <aMlb5x0eWA4rpVKe@laps>
Date: Tue, 16 Sep 2025 08:45:27 -0400
From: Sasha Levin <sashal@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Donet Tom <donettom@...ux.ibm.com>,
	David Hildenbrand <david@...hat.com>,
	Ritesh Harjani <ritesh.list@...il.com>,
	Xu Xin <xu.xin16@....com.cn>,
	Chengming Zhou <chengming.zhou@...ux.dev>,
	Wei Yang <richard.weiyang@...il.com>,
	Aboorva Devarajan <aboorvad@...ux.ibm.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	Giorgi Tchankvetadze <giorgitchankvetadze1997@...il.com>,
	stable@...r.kernel.org, Joe Perches <joe@...ches.com>
Subject: Re: [PATCH v2 1/3] mm/ksm: Fix incorrect KSM counter handling in
 mm_struct during fork

On Mon, Sep 15, 2025 at 09:41:17PM -0700, Andrew Morton wrote:
>On Tue, 16 Sep 2025 00:33:09 -0400 Sasha Levin <sashal@...nel.org> wrote:
>> On Mon, Sep 15, 2025 at 04:42:48PM -0700, Andrew Morton wrote:
>> >I think the most important use for Fixes: is to tell the -stable
>> >maintainers which kernel version(s) we believe should receive the
>> >patch.  So listing multiple Fixes: targets just causes confusion.
>>
>> Right - there's no way of communicating if all the commits listed in multiple
>> Fixes tags should exist in the tree, or any one of them, for the new fix to be
>> applicable.
>
>So what should we do in this situation?

For us, ideally point to the oldest commit fixed by the new commit with a
Fixes: tag, and then a note along with the stable tag if this is a more complex
scenario that we need to consider.

-- 
Thanks,
Sasha