From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/8] mm/memory-failure.c: fix race with changing page more robustly
Date: Sun, 20 Feb 2022 23:43:18 +0000 [thread overview]
Message-ID: <20220220234316.GA3968455@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20220218090118.1105-5-linmiaohe@huawei.com>
On Fri, Feb 18, 2022 at 05:01:14PM +0800, Miaohe Lin wrote:
> We're only intended to deal with the non-Compound page after we split thp
> in memory_failure. However, the page could have changed compound pages due
> to race window. If this happens, we could retry once to hopefully handle
> the page next round. Also remove unneeded orig_head. It's always equal to
> the hpage. So we can use hpage directly and remove this redundant one.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
> ---
> mm/memory-failure.c | 20 +++++++++++++++-----
> 1 file changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index 7e205d91b2d7..2ca50cfa601f 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -1690,7 +1690,6 @@ int memory_failure(unsigned long pfn, int flags)
> {
> struct page *p;
> struct page *hpage;
> - struct page *orig_head;
> struct dev_pagemap *pgmap;
> int res = 0;
> unsigned long page_flags;
> @@ -1736,7 +1735,7 @@ int memory_failure(unsigned long pfn, int flags)
> goto unlock_mutex;
> }
>
> - orig_head = hpage = compound_head(p);
> + hpage = compound_head(p);
> num_poisoned_pages_inc();
>
> /*
> @@ -1817,10 +1816,21 @@ int memory_failure(unsigned long pfn, int flags)
> lock_page(p);
>
> /*
> - * The page could have changed compound pages during the locking.
> - * If this happens just bail out.
> + * We're only intended to deal with the non-Compound page here.
> + * However, the page could have changed compound pages due to
> + * race window. If this happens, we could try again to hopefully
> + * handle the page next round.
> */
> - if (PageCompound(p) && compound_head(p) != orig_head) {
> + if (PageCompound(p)) {
> + if (retry) {
> + if (TestClearPageHWPoison(p))
> + num_poisoned_pages_dec();
> + unlock_page(p);
> + put_page(p);
> + flags &= ~MF_COUNT_INCREASED;
> + retry = false;
> + goto try_again;
> + }
> action_result(pfn, MF_MSG_DIFFERENT_COMPOUND, MF_IGNORED);
> res = -EBUSY;
> goto unlock_page;
> --
> 2.23.0
next prev parent reply other threads:[~2022-02-20 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 9:01 [PATCH v3 0/8] A few cleanup and fixup patches for memory failure Miaohe Lin
2022-02-18 9:01 ` [PATCH v3 1/8] mm/memory-failure.c: minor clean up for memory_failure_dev_pagemap Miaohe Lin
2022-02-18 9:01 ` [PATCH v3 2/8] mm/memory-failure.c: catch unexpected -EFAULT from vma_address() Miaohe Lin
2022-02-18 9:01 ` [PATCH v3 3/8] mm/memory-failure.c: rework the signaling logic in kill_proc Miaohe Lin
2022-02-18 9:01 ` [PATCH v3 4/8] mm/memory-failure.c: fix race with changing page more robustly Miaohe Lin
2022-02-20 23:43 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2022-02-18 9:01 ` [PATCH v3 5/8] mm/memory-failure.c: remove PageSlab check in hwpoison_filter_dev Miaohe Lin
2022-02-18 9:01 ` [PATCH v3 6/8] mm/memory-failure.c: rework the try_to_unmap logic in hwpoison_user_mappings() Miaohe Lin
2022-02-18 9:01 ` [PATCH v3 7/8] mm/memory-failure.c: remove obsolete comment in __soft_offline_page Miaohe Lin
2022-02-18 9:01 ` [PATCH v3 8/8] mm/memory-failure.c: remove unnecessary PageTransTail check 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=20220220234316.GA3968455@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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