linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Miaohe Lin <linmiaohe@huawei.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] mm: memory-failure: make action_result() return int
Date: Mon, 24 Oct 2022 09:39:20 +0800	[thread overview]
Message-ID: <e803ec8e-a20a-949c-88b0-aee250f98208@huawei.com> (raw)
In-Reply-To: <20221023235633.GC4024629@hori.linux.bs1.fc.nec.co.jp>


On 2022/10/24 7:56, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Fri, Oct 21, 2022 at 04:46:11PM +0800, Kefeng Wang wrote:
>> Check mf_result in action_result(), only return 0 when MF_RECOVERED,
>> or return -EBUSY, which will simplify code a bit.
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> Thanks for the cleanup, Kefeng.
> I basically agree with the change. I have one comment below ...
>
>> ---
>>   mm/memory-failure.c | 42 ++++++++++++++++--------------------------
>>   1 file changed, 16 insertions(+), 26 deletions(-)
>>
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index ca0199d0f79d..3f469e2da047 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -1182,14 +1182,16 @@ static struct page_state error_states[] = {
>>    * "Dirty/Clean" indication is not 100% accurate due to the possibility of
>>    * setting PG_dirty outside page lock. See also comment above set_page_dirty().
>>    */
>> -static void action_result(unsigned long pfn, enum mf_action_page_type type,
>> -			  enum mf_result result)
>> +static int action_result(unsigned long pfn, enum mf_action_page_type type,
>> +			 enum mf_result result)
>>   {
>>   	trace_memory_failure_event(pfn, type, result);
>>   
>>   	num_poisoned_pages_inc();
>>   	pr_err("%#lx: recovery action for %s: %s\n",
>>   		pfn, action_page_types[type], action_name[result]);
>> +
>> +	return result == MF_RECOVERED ? 0 : -EBUSY;
> I think that MF_DELAYED may be considered as success (returning 0), then
> page_action() can be cleaned up a little more (like below?)
Yes, MF_DELAYED should be considered as success,
>
>      static int page_action(struct page_state *ps, struct page *p,
>                              unsigned long pfn)
>      {
>              int result;
>      
>              /* page p should be unlocked after returning from ps->action().  */
>              result = ps->action(ps, p);
>      
>              /* Could do more checks here if page looks ok */
>              /*
>               * Could adjust zone counters here to correct for the missing page.
>               */
>      
>              return action_result(pfn, ps->type, result);
>      }
>
> Existing direct callers (I mean action_result() called from other than
> page_action()) are never called with result==MF_DELAYED, so this change
> should not affect them.
I will refresh this patch, thanks.
> Does it make sense for you?
>
> Thanks,
> Naoya Horiguchi


  reply	other threads:[~2022-10-24  1:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  8:46 [PATCH 1/3] mm: memory-failure: make put_ref_page() more useful Kefeng Wang
2022-10-21  8:46 ` [PATCH 2/3] mm: memory-failure: avoid pfn_valid() twice in soft_offline_page() Kefeng Wang
2022-10-23 23:39   ` HORIGUCHI NAOYA(堀口 直也)
2022-10-25  2:55   ` Miaohe Lin
2022-10-21  8:46 ` [PATCH 3/3] mm: memory-failure: make action_result() return int Kefeng Wang
2022-10-23 23:56   ` HORIGUCHI NAOYA(堀口 直也)
2022-10-24  1:39     ` Kefeng Wang [this message]
2022-10-24  3:51   ` [PATCH v2] " Kefeng Wang
2022-10-24  7:35     ` HORIGUCHI NAOYA(堀口 直也)
2022-10-25  3:07     ` Miaohe Lin
2022-10-23 23:38 ` [PATCH 1/3] mm: memory-failure: make put_ref_page() more useful HORIGUCHI NAOYA(堀口 直也)
2022-10-25  2:52 ` Miaohe Lin

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=e803ec8e-a20a-949c-88b0-aee250f98208@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@nec.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