linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: <naoya.horiguchi@nec.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: memory-failure: fix unexpected return value in soft_offline_page()
Date: Tue, 27 Jun 2023 12:30:46 -0700	[thread overview]
Message-ID: <20230627123046.ef7e791208214bbfecd71e42@linux-foundation.org> (raw)
In-Reply-To: <20230627112808.1275241-1-linmiaohe@huawei.com>

On Tue, 27 Jun 2023 19:28:08 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:

> When page_handle_poison() fails to handle the hugepage or free page in
> retry path, soft_offline_page() will return 0 while -EBUSY is expected
> in this case.

What are the user visible effects of the bug?

> Fixes: b94e02822deb ("mm,hwpoison: try to narrow window race for free pages")
>
> ...
>
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -2737,10 +2737,13 @@ int soft_offline_page(unsigned long pfn, int flags)
>  	if (ret > 0) {
>  		ret = soft_offline_in_use_page(page);
>  	} else if (ret == 0) {
> -		if (!page_handle_poison(page, true, false) && try_again) {
> -			try_again = false;
> -			flags &= ~MF_COUNT_INCREASED;
> -			goto retry;
> +		if (!page_handle_poison(page, true, false)) {
> +			if (try_again) {
> +				try_again = false;
> +				flags &= ~MF_COUNT_INCREASED;
> +				goto retry;
> +			}
> +			ret = -EBUSY;
>  		}
>  	}


  reply	other threads:[~2023-06-27 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 11:28 Miaohe Lin
2023-06-27 19:30 ` Andrew Morton [this message]
2023-06-28  1:56   ` Miaohe Lin
2023-06-28 11:06     ` Naoya Horiguchi
2023-06-29  1:48       ` 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=20230627123046.ef7e791208214bbfecd71e42@linux-foundation.org \
    --to=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