mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xin Hao <xhao@linux.alibaba.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: 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: Sun, 5 Jun 2022 13:25:00 +0800	[thread overview]
Message-ID: <a64d6c6b-ae07-ed49-8185-0381b6e2d37b@linux.alibaba.com> (raw)
In-Reply-To: <Ypt1eFD5QDteH1RS@casper.infradead.org>

Hi, Matthew:

On 6/4/22 11:08 PM, Matthew Wilcox wrote:
> 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?

Yes, about the skip_kasan_poison, i just want the kpageflags to support 
it,  i think it should be included,

the mainly  region is i want get the page node info from the kpageflags 
in my next patch,  when i check these

codes,  i see there lost some info about the skip_kasan_poison and young 
flags,  the page_types tool also check

the kasan pages, so i think it should be included.

Thanks.

-- 
Best Regards!
Xin Hao


      reply	other threads:[~2022-06-05  5:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 15:43 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
2022-06-05  5:25       ` Xin Hao [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=a64d6c6b-ae07-ed49-8185-0381b6e2d37b@linux.alibaba.com \
    --to=xhao@linux.alibaba.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®