From: Zenghui Yu <zenghui.yu@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
ljs@kernel.org, liam@infradead.org, vbabka@kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
corbet@lwn.net, skhan@linuxfoundation.org
Subject: Re: [PATCH] docs: pagemap: fix flags location, member name and sample code
Date: Sat, 27 Jun 2026 00:03:58 +0800 [thread overview]
Message-ID: <cf3abe7b-686a-462c-9203-02187ced058b@linux.dev> (raw)
In-Reply-To: <511c2e7c-0305-4917-a639-e8e9e8710903@kernel.org>
On 6/26/26 10:47 PM, David Hildenbrand (Arm) wrote:
> On 6/25/26 19:44, Zenghui Yu wrote:
> > The userland visible page flags (KPF_*) were initially moved to
> > include/linux/kernel-page-flags.h in commit 1a9b5b7fe0c5 ("mm: export
> > stable page flags"), and later moved to
> > include/uapi/linux/kernel-page-flags.h in commit 607ca46e97a1 ("UAPI:
> > (Scripted) Disintegrate include/linux"). Upadte the doc to reflect the
>
> s/Upadte/Update/
>
> > current location of these flags.
>
> Ack
>
> >
> > The member @walk_end of struct pm_scan_arg {} was wrongly written as
> > "end_walk".
>
> Ack
>
> >
> > The first sample code of the PAGEMAP_SCAN ioctl wrongly used the
> > PM_SCAN_CHECK_WPASYNC flag twice, instead of the PM_SCAN_WP_MATCHING flag.
>
> That makes sense.
>
> > The second one missed PAGE_IS_FILE in the required mask.
>
> Hm. The description says: "Find pages which have been written, are file backed,
> not swapped and either present or huge".
>
> But doesn't that mean that
>
> it should actually be
>
> .category_mask = PAGE_IS_WRITTEN | PAGE_IS_FILE,
>
> Because
>
> .category_inverted = PAGE_IS_SWAPPED,
Ah! Thanks for pointing it out. I'll fix it soon.
Thanks,
Zenghui
prev parent reply other threads:[~2026-06-26 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 17:44 [PATCH] docs: pagemap: fix flags location, member name and sample code Zenghui Yu
2026-06-26 0:04 ` SeongJae Park
2026-06-26 14:47 ` David Hildenbrand (Arm)
2026-06-26 16:03 ` Zenghui Yu [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=cf3abe7b-686a-462c-9203-02187ced058b@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.