From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: zhenwei pi <pizhenwei@bytedance.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"david@redhat.com" <david@redhat.com>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH v6 1/1] mm/memory-failure: disable unpoison once hw error happens
Date: Wed, 15 Jun 2022 22:58:14 +0000 [thread overview]
Message-ID: <20220615225814.GA1685347@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20220615134933.66f3ba7f3b169b936b2128de@linux-foundation.org>
On Wed, Jun 15, 2022 at 01:49:33PM -0700, Andrew Morton wrote:
> On Wed, 15 Jun 2022 10:34:06 +0000 HORIGUCHI NAOYA(堀口 直也) <naoya.horiguchi@nec.com> wrote:
>
> > On Wed, Jun 15, 2022 at 05:32:09PM +0800, zhenwei pi wrote:
> > > Currently unpoison_memory(unsigned long pfn) is designed for soft
> > > poison(hwpoison-inject) only. Since 17fae1294ad9d, the KPTE gets
> > > cleared on a x86 platform once hardware memory corrupts.
> > >
> > > Unpoisoning a hardware corrupted page puts page back buddy only,
> > > the kernel has a chance to access the page with *NOT PRESENT* KPTE.
> > > This leads BUG during accessing on the corrupted KPTE.
> > >
> > > Suggested by David&Naoya, disable unpoison mechanism when a real HW error
> > > happens to avoid BUG like this:
> > >
> >
> > ...
> >
> > >
> > > Fixes: 847ce401df392 ("HWPOISON: Add unpoisoning support")
> > > Fixes: 17fae1294ad9d ("x86/{mce,mm}: Unmap the entire page if the whole page is affected and poisoned")
> > > Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
> > > Cc: David Hildenbrand <david@redhat.com>
> > > Cc: Oscar Salvador <osalvador@suse.de>
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Acked-by: David Hildenbrand <david@redhat.com>
> > > Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> >
> > Thank you very much.
> >
> > Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
>
> I added cc:stable to this. But the dual Fixes: are going to confuse
> people regarding which kernel versions need the fix. Can we be more
> specific?
OK. This bug was visible since 17fae1294ad9d (merged in v5.8 time period),
so marking "v5.8+" on "Cc: stable" line would be helpful.
- Naoya Horiguchi
next prev parent reply other threads:[~2022-06-15 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 9:32 [PATCH v6 0/1] mm/memory-failure: don't allow to unpoison hw corrupted page zhenwei pi
2022-06-15 9:32 ` [PATCH v6 1/1] mm/memory-failure: disable unpoison once hw error happens zhenwei pi
2022-06-15 10:34 ` HORIGUCHI NAOYA(堀口 直也)
2022-06-15 20:49 ` Andrew Morton
2022-06-15 22:58 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2022-06-16 4:01 ` Oscar Salvador
2022-06-16 8:30 ` 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=20220615225814.GA1685347@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=pizhenwei@bytedance.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