[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a64d6c6b-ae07-ed49-8185-0381b6e2d37b@linux.alibaba.com>
Date: Sun, 5 Jun 2022 13:25:00 +0800
From: Xin Hao <xhao@...ux.alibaba.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: sashal@...nel.org, akpm@...ux-foundation.org, adobriyan@...il.com,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] proc: export page young and skip_kasan_poison flag via
kpageflags
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
Powered by blists - more mailing lists