From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Jinjiang Tu <tujinjiang@huawei.com>
Cc: ziy@nvidia.com, luizcap@redhat.com, willy@infradead.org,
linmiaohe@huawei.com, svetly.todorov@memverge.com,
xu.xin16@zte.com.cn, chengming.zhou@linux.dev,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
wangkefeng.wang@huawei.com, sunnanyong@huawei.com
Subject: Re: [PATCH] fs/proc: fix KPF_KSM reported for all anonymous pages
Date: Thu, 25 Jun 2026 08:38:28 +0200 [thread overview]
Message-ID: <45a5df08-6a92-4dd7-8ee0-12c32154dbf8@kernel.org> (raw)
In-Reply-To: <20260624180051.134da6553b4f0c4c2785f730@linux-foundation.org>
On 6/25/26 03:00, Andrew Morton wrote:
> On Tue, 23 Jun 2026 09:37:57 +0800 Jinjiang Tu <tujinjiang@huawei.com> wrote:
>
>>> This only affects /proc/kpageflags (well, and hwpoison inject on a weird testing
>>> interface), so it's not really that relevant for real workloads (debugging and
>>> testing).
>>>
>>> So not sure whether we should CC:stable. Likely not.
>>
>> /proc/kpageflags is generally used only for analysis and is unlikely to be
>> used in production environments. I found this issue due to I was analyzing
>> pfns allocated by which stacks are KSM-merged. So I think it's unnecessary
>> to CC:stable.
>
> Well, it's a bug. The fix is super-simple so I think it's reasonable
> to feed it back to users of earlier kernels.
Definitely doesn't hurt.
--
Cheers,
David
next prev parent reply other threads:[~2026-06-25 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 9:15 [PATCH] fs/proc: fix KPF_KSM reported for all anonymous pages Jinjiang Tu
2026-06-22 11:45 ` David Hildenbrand (Arm)
2026-06-22 12:00 ` David Hildenbrand (Arm)
2026-06-23 1:37 ` Jinjiang Tu
2026-06-25 1:00 ` Andrew Morton
2026-06-25 6:38 ` David Hildenbrand (Arm) [this message]
2026-06-25 6:39 ` David Hildenbrand (Arm)
2026-06-25 11:21 ` Jinjiang Tu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45a5df08-6a92-4dd7-8ee0-12c32154dbf8@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luizcap@redhat.com \
--cc=sunnanyong@huawei.com \
--cc=svetly.todorov@memverge.com \
--cc=tujinjiang@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=xu.xin16@zte.com.cn \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox