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: <04f8db38-9a53-a81a-82ac-21653f795e08@huawei.com>
Date: Wed, 17 Jul 2024 15:48:52 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: Michal Hocko <mhocko@...e.com>
CC: <akpm@...ux-foundation.org>, <nao.horiguchi@...il.com>,
	<linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] mm/hwpoison: reset hwpoison filter parameters in
 pfn_inject_exit()

On 2024/7/17 15:25, Michal Hocko wrote:
> On Wed 17-07-24 14:59:40, Miaohe Lin wrote:
>> On 2024/7/17 14:18, Michal Hocko wrote:
> [...]
>>> Why does this need to be done through different modules? Why it cannot
>>> be part of the memory-filure.c?
>>
>> This is a bold idea for me. :) I think it can be part of the memory-filure.c.
>> So CONFIG_HWPOISON_INJECT should be removed from the world and then make
>> hwpoison-inject default on when MEMORY_FAILURE is configured?
> 
> I would start by moving code into mm/hwpoison-inject.c. Whether this
> should also remove CONFIG_HWPOISON_INJECT is a different question. I
> am not really sure a debugfs interface warrants a config option. Anyway
> two things for two separate patches
> 

Thanks for your suggestion. :) Will try to do it when I am free.
Thanks.
.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ