From: "zhen.ni" <zhen.ni@easystack.cn>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: vbabka@kernel.org, surenb@google.com, mhocko@suse.com,
jackmanb@google.com, hannes@cmpxchg.org, ziy@nvidia.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering
Date: Wed, 6 May 2026 11:16:04 +0800 [thread overview]
Message-ID: <0f0d9a2d-47a9-4150-ac97-83a92ce8c048@easystack.cn> (raw)
In-Reply-To: <20260430112245.be3189f09bd6a71970a74746@linux-foundation.org>
在 2026/5/1 02:22, Andrew Morton 写道:
> On Fri, 1 May 2026 00:32:44 +0800 Zhen Ni <zhen.ni@easystack.cn> wrote:
>
>> This patch series introduces filtering capabilities to the page_owner
>> feature to address storage and performance challenges in production
>> environments.
>
> AI review asks a couple of reasonable-sounding questions:
> https://sashiko.dev/#/patchset/20260430163247.13628-1-zhen.ni@easystack.cn
>
>
Will this cause KCSAN splats?
While the practical impact is minimal (debugfs interface, infrequent
writes, torn reads only cause temporary debug output inconsistency),
we should properly handle this to avoid KCSAN warnings.
I'm wondering if using the __data_racy qualifier would be appropriate
here? Something like:
struct page_owner_filter {
...
nodemask_t __data_racy nid_mask;
};
Is it necessary to evaluate nodes_empty(mask) inside this loop?
I'll fix this by moving the check outside the loop.
Best regards,
Zhen
prev parent reply other threads:[~2026-05-06 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 16:32 [PATCH v4 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering Zhen Ni
2026-04-30 16:32 ` [PATCH v4 1/3] mm/page_owner: add print_mode filter Zhen Ni
2026-04-30 16:32 ` [PATCH v4 2/3] mm/page_owner: add NUMA node filter with nodelist support Zhen Ni
2026-04-30 16:32 ` [PATCH v4 3/3] mm/page_owner: document page_owner filter features Zhen Ni
2026-04-30 18:22 ` [PATCH v4 0/3] mm/page_owner: add filter infrastructure for print_mode and NUMA filtering Andrew Morton
2026-05-01 0:12 ` SeongJae Park
2026-05-06 3:16 ` zhen.ni [this message]
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=0f0d9a2d-47a9-4150-ac97-83a92ce8c048@easystack.cn \
--to=zhen.ni@easystack.cn \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--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