linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <nao.horiguchi@gmail.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/hwpoison: reset hwpoison filter parameters in pfn_inject_exit()
Date: Tue, 16 Jul 2024 10:37:54 +0800	[thread overview]
Message-ID: <29487e61-8785-0064-6208-5044b6419c9c@huawei.com> (raw)
In-Reply-To: <20240715133338.fb8b3b9a99f05b086fc54b82@linux-foundation.org>

On 2024/7/16 4:33, Andrew Morton wrote:
> On Mon, 15 Jul 2024 18:28:06 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:
> 
>> When hwpoison_inject module is removed, hwpoison_filter_* parameters
>> should be reset. Otherwise these parameters will have non-default values
>> at next insmod time.
>>
>> ...
>>
>> --- a/mm/hwpoison-inject.c
>> +++ b/mm/hwpoison-inject.c
>> @@ -64,9 +64,20 @@ static int hwpoison_unpoison(void *data, u64 val)
>>  DEFINE_DEBUGFS_ATTRIBUTE(hwpoison_fops, NULL, hwpoison_inject, "%lli\n");
>>  DEFINE_DEBUGFS_ATTRIBUTE(unpoison_fops, NULL, hwpoison_unpoison, "%lli\n");
>>  
>> -static void __exit pfn_inject_exit(void)
>> +static inline void reset_hwpoison_filter(void)
>>  {
>>  	hwpoison_filter_enable = 0;
>> +	hwpoison_filter_dev_major = ~0U;
>> +	hwpoison_filter_dev_minor = ~0U;
>> +	hwpoison_filter_flags_mask = 0;
>> +	hwpoison_filter_flags_value = 0;
>> +#ifdef CONFIG_MEMCG
>> +	hwpoison_filter_memcg = 0;
>> +#endif
>> +}
>> +
>> +static void __exit pfn_inject_exit(void)
>> +{
>>  	debugfs_remove_recursive(hwpoison_dir);
>>  }
> 
> The new reset_hwpoison_filter() has no callers?

I'm sorry but I can't figure out why that's missed. I remember I tested this patch
and queued it... Will send a new version and re-test it.
Thanks.
.


      reply	other threads:[~2024-07-16  2:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 10:28 Miaohe Lin
2024-07-15 20:33 ` Andrew Morton
2024-07-16  2:37   ` Miaohe Lin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29487e61-8785-0064-6208-5044b6419c9c@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nao.horiguchi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox