linux-kernel - Re: [PATCH v4 1/2] mm/memory-failure: introduce "hwpoisoned-pages" entry

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: <c436f65d-d219-d2a5-0275-462b3a10879e@huawei.com>
Date:   Tue, 14 Jun 2022 16:19:26 +0800
From:   Miaohe Lin <linmiaohe@...wei.com>
To:     David Hildenbrand <david@...hat.com>,
        HORIGUCHI NAOYA(堀口 直也) 
        <naoya.horiguchi@....com>
CC:     "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        zhenwei pi <pizhenwei@...edance.com>
Subject: Re: [PATCH v4 1/2] mm/memory-failure: introduce "hwpoisoned-pages"
 entry

On 2022/6/14 15:13, David Hildenbrand wrote:
> 	   &hwpoisoned_pages);
>>
>> I'm not sure how useful this interface from userspace (controlling test process
>> with this?).  Do we really need to expose this to userspace? 
>>
>>
>> TBH I feel that another approach like below is more desirable:
>>
>>   - define a new flag in "enum mf_flags" (for example named MF_SW_SIMULATED),
>>   - set the flag when calling memory_failure() from the three callers
>>     mentioned above,
>>   - define a global variable (typed bool) in mm/memory_failure.c_to show that
>>     the system has experienced a real hardware memory error events.
>>   - once memory_failure() is called without MF_SW_SIMULATED, the new global
>>     bool variable is set, and afterward unpoison_memory always fails with
>>     -EOPNOTSUPP.
> 
> Exactly what I had in mind.

This approach should be more straightforward. ;)

>