From: Matthew Wilcox <willy@infradead.org>
To: Xin Hao <xhao@linux.alibaba.com>
Cc: changbin.du@intel.com, sashal@kernel.org,
akpm@linux-foundation.org, adobriyan@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: export page young and skip_kasan_poison flag via kpageflags
Date: Sat, 4 Jun 2022 16:08:40 +0100 [thread overview]
Message-ID: <Ypt1eFD5QDteH1RS@casper.infradead.org> (raw)
In-Reply-To: <55263fe2-f8ae-f681-69fd-1064a74f2bb6@linux.alibaba.com>
On Sat, Jun 04, 2022 at 05:50:31PM +0800, Xin Hao wrote:
>
> On 6/3/22 2:28 AM, Matthew Wilcox wrote:
> > On Thu, Jun 02, 2022 at 11:43:02PM +0800, Xin Hao wrote:
> > > Now the young and skip_kasan_poison flag are supported in
> > Why do we want userspace to know about whether skip_kasan_poison is set?
> > That seems like a kernel-internal detail to me.
>
> the skip_kasan_poison also a page flags, we use page_types tool to display
> them not only include user-internal,
>
> but also kernel-internal, add them, the page-types tool can more detail
> display the kernel-internal page flags,
>
> just in case we don't miss some page flags when check the whole memory.
So you're just being completist? You don't have a reason to expose this
information?
next prev parent reply other threads:[~2022-06-04 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:43 [PATCH] proc: export page young and skip_kasan_poison flag via kpageflags Xin Hao
2022-06-02 18:04 ` Andrew Morton
2022-06-04 9:51 ` Xin Hao
2022-06-02 18:28 ` Matthew Wilcox
2022-06-04 9:50 ` Xin Hao
2022-06-04 15:08 ` Matthew Wilcox [this message]
2022-06-05 5:25 ` Xin Hao
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=Ypt1eFD5QDteH1RS@casper.infradead.org \
--to=willy@infradead.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=changbin.du@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=xhao@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).