From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Yang Shi <shy828301@gmail.com>
Cc: Naoya Horiguchi <naoya.horiguchi@linux.dev>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>,
Oscar Salvador <osalvador@suse.de>,
Muchun Song <songmuchun@bytedance.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Michal Hocko <mhocko@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] mm/hwpoison: Retry with shake_page() for unhandlable pages
Date: Thu, 19 Aug 2021 00:13:10 +0000 [thread overview]
Message-ID: <20210819001310.GA535269@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <CAHbLzkrHOHNRQU-TtR6cV9stV-c88jxg+LWbJBbBifh1n74FKw@mail.gmail.com>
On Wed, Aug 18, 2021 at 11:07:43AM -0700, Yang Shi wrote:
> On Mon, Aug 16, 2021 at 10:37 PM Naoya Horiguchi
> <naoya.horiguchi@linux.dev> wrote:
> >
> > From: Naoya Horiguchi <naoya.horiguchi@nec.com>
> >
> > HWPoisonHandlable() sometimes returns false for typical user pages
> > due to races with average memory events like transfers over LRU lists.
> > This causes failures in hwpoison handling.
> >
> > There's retry code for such a case but does not work because the retry
> > loop reaches the retry limit too quickly before the page settles down to
> > handlable state. Let get_any_page() call shake_page() to fix it.
> >
> > Fixes: 25182f05ffed ("mm,hwpoison: fix race with hugetlb page allocation")
> > Reported-by: Tony Luck <tony.luck@intel.com>
> > Signed-off-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
> > Cc: stable@vger.kernel.org # 5.13
> > ---
> > mm/memory-failure.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
> >
> > diff --git v5.14-rc6/mm/memory-failure.c v5.14-rc6_patched/mm/memory-failure.c
> > index eefd823deb67..aa6592540f17 100644
> > --- v5.14-rc6/mm/memory-failure.c
> > +++ v5.14-rc6_patched/mm/memory-failure.c
> > @@ -1146,7 +1146,7 @@ static int __get_hwpoison_page(struct page *page)
> > * unexpected races caused by taking a page refcount.
> > */
> > if (!HWPoisonHandlable(head))
> > - return 0;
> > + return -EBUSY;
> >
> > if (PageTransHuge(head)) {
> > /*
> > @@ -1199,9 +1199,14 @@ static int get_any_page(struct page *p, unsigned long flags)
> > }
> > goto out;
> > } else if (ret == -EBUSY) {
> > - /* We raced with freeing huge page to buddy, retry. */
> > - if (pass++ < 3)
> > + /*
> > + * We raced with (possibly temporary) unhandlable
> > + * page, retry.
> > + */
> > + if (pass++ < 3) {
> > + shake_page(p, 1);
> > goto try_again;
> > + }
>
> I think the return value should be set to -EIO before jumping to out.
> I'm supposed -EIO means this is really or very likely an unhandlable
> page.
You're right, I have the same assumption that -EBUSY means transient error
and -EIO means permanent one. And we consider an error as permanent when the
retry limit is reached. I'll update the patch. Thank you for the comment.
- Naoya Horiguchi
prev parent reply other threads:[~2021-08-19 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 5:37 Naoya Horiguchi
2021-08-18 18:07 ` Yang Shi
2021-08-19 0:13 ` HORIGUCHI NAOYA(堀口 直也) [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=20210819001310.GA535269@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@linux.dev \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=tony.luck@intel.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