[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d7be334af3944f990b56c80a70b7691763c3af8.camel@perches.com>
Date: Mon, 15 Sep 2025 19:14:47 -0700
From: Joe Perches <joe@...ches.com>
To: Andrew Morton <akpm@...ux-foundation.org>, Donet Tom
<donettom@...ux.ibm.com>
Cc: 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
Subject: Re: [PATCH v2 1/3] mm/ksm: Fix incorrect KSM counter handling in
mm_struct during fork
On Mon, 2025-09-15 at 16:42 -0700, Andrew Morton wrote:
> On Mon, 15 Sep 2025 20:33:04 +0530 Donet Tom <donettom@...ux.ibm.com> wrote:
[]
> > Fixes: 7609385337a4 ("ksm: count ksm merging pages for each process")
>
> Linux-v5.19
>
> > Fixes: cb4df4cae4f2 ("ksm: count allocated ksm rmap_items for each process")
>
> Linux-v6.1
>
> > Fixes: e2942062e01d ("ksm: count all zero pages placed by KSM")
>
> Linux-v6.10
>
> > cc: stable@...r.kernel.org # v6.6
>
> So how was Linux-v6.6 arrived at?
[]
> (Cc Joe. Should checkpatch say something about this)?
Probably not. Parsing variants of versions seems, umm, difficult.
Powered by blists - more mailing lists