From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Naoya Horiguchi <naoya.horiguchi@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Youquan Song <youquan.song@intel.com>
Subject: Re: [PATCH] mm/hwpoison: Fix error page recovered but reported "not recovered"
Date: Thu, 13 Jan 2022 06:52:15 +0000 [thread overview]
Message-ID: <20220113065211.GA2947732@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <Yd+H00eSqZb+RsTv@agluck-desk2.amr.corp.intel.com>
On Wed, Jan 12, 2022 at 06:00:51PM -0800, Luck, Tony wrote:
> On Wed, Jan 12, 2022 at 09:11:45PM +0900, Naoya Horiguchi wrote:
> > On Fri, Jan 07, 2022 at 11:44:50AM -0800, Tony Luck wrote:
> > > From: Youquan Song <youquan.song@intel.com>
>
> > diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> > index 14ae5c18e776..4c9bd1d37301 100644
> > --- a/mm/memory-failure.c
> > +++ b/mm/memory-failure.c
> > @@ -707,8 +707,10 @@ static int kill_accessing_process(struct task_struct *p, unsigned long pfn,
> > (void *)&priv);
> > if (ret == 1 && priv.tk.addr)
> > kill_proc(&priv.tk, pfn, flags);
> > + else
> > + ret = 0;
> > mmap_read_unlock(p->mm);
> > - return ret ? -EFAULT : -EHWPOISON;
> > + return ret > 0 ? -EHWPOISON : -EFAULT;
> > }
> >
> > static const char *action_name[] = {
>
> Yes. This fixes the problem (and your explanation helped
> me understand this code better).
>
Thank you for confirming. I just sent v2.
> Fell free to take any words you need from the original patch
> comment and switch to:
>
> Reported-by: Youquan Song <youquan.song@intel.com>
>
> Thanks for looking (and fixing!)
Your welcome :)
- Naoya
prev parent reply other threads:[~2022-01-13 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 19:44 Tony Luck
2022-01-12 12:11 ` Naoya Horiguchi
2022-01-13 2:00 ` Luck, Tony
2022-01-13 6:52 ` 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=20220113065211.GA2947732@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=naoya.horiguchi@linux.dev \
--cc=tony.luck@intel.com \
--cc=youquan.song@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