linux-kernel - Re: [PATCH] proc: export page young and skip_kasan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Ypt1eFD5QDteH1RS@casper.infradead.org>
Date:   Sat, 4 Jun 2022 16:08:40 +0100
From:   Matthew Wilcox <willy@...radead.org>
To:     Xin Hao <xhao@...ux.alibaba.com>
Cc:     changbin.du@...el.com, 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

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?