linux-kernel - Re: Re: [PATCH] mm: hugetlbfs: add hwcrp_hugepages to record memory failure on hugetlbfs

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20210609022311.2102-1-wangbin224@huawei.com>
Date:   Wed, 9 Jun 2021 10:23:11 +0800
From:   wangbin <wangbin224@...wei.com>
To:     <naoya.horiguchi@....com>
CC:     <akpm@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
        <linux-mm@...ck.org>, <mike.kravetz@...cle.com>,
        <nao.horiguchi@...il.com>, <wangbin224@...wei.com>,
        <wuxu.wu@...wei.com>
Subject: Re: Re: [PATCH] mm: hugetlbfs: add hwcrp_hugepages to record memory failure on hugetlbfs

> If you can use root privilege in your use-case, an easy way to get the
> number of corrupted hugepages is to use page-types.c (which reads
> /proc/kpageflags) like below:
> 
>     $ page-types -b huge,hwpoison=huge,hwpoison
>                  flags      page-count       MB  symbolic-flags                     long-symbolic-flags
>     0x00000000000a8000               1        0  _______________H_G_X_______________________        compound_head,huge,hwpoison
>                  total               1        0
> 
> But I guess that many usecases do not permit access to this interface,
> where some new accounting interface for corrupted hugepages could be
> helpful as you suggest.

Thanks for your suggestion very much. This approach is helpful to me.
But as you say, root privilege is not permitted in most cases. And I
also want to know the number of corrupted hugepages per node.

--
Bin Wang