From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Naoya Horiguchi <nao.horiguchi@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Aili Yao <yaoaili@kingsoft.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@redhat.com>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
Jue Wang <juew@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] mm,hwpoison: fix sending SIGBUS for Action Required MCE
Date: Fri, 7 May 2021 05:24:22 +0000 [thread overview]
Message-ID: <20210507052422.GB2158342@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <87ba79daaba1416589b203118be096cb@intel.com>
On Fri, May 07, 2021 at 03:37:07AM +0000, Luck, Tony wrote:
> >> I updated the series based on previous feedbacks/discussions.
> >
> > Tested-by: Tony Luck <tony.luck@intel.com>
>
> Maybe this series should get a "Cc: stable" tag too?
The second patch (I squashed 2/3 and 3/3 into one in v4) is a little
too large (more than 100 lines of change), which doesn't meet stable rule.
But the first patch looks suitable to me for stable.
>
> I don't have a specific commit to provide for Fixes:, but it deals
> with an issue where sometimes processes return from the machine
> check handler and hit the same machine check again.
If we consider that this issue is visible after LMCE is supported,
the following commit could be the target of Fixes tag.
commit 243d657eaf540db882f73497060da5a4f7d86a90
Author: Ashok Raj <ashok.raj@intel.com>
Date: Thu Jun 4 18:55:24 2015 +0200
x86/mce: Handle Local MCE events
but according to your test result, any other factor might affect when
the issue actually got reproducible.
>
> It's hard[1] to hit in v5.8, but somehow gets progressively easier in
> newer versions.
>
> -Tony
>
> [1] Initially I thought it didn't happen at all in v5.8. Then wasted a bunch
> of time trying to bisect. But my "git bisect good" responses turned out to
> be randomly assigned when I just hadn't tried enough times to make the
> problem show up.
Thanks for time and effort for testing.
- Naoya
next prev parent reply other threads:[~2021-05-07 5:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 0:57 [PATCH v3 0/3] mm,hwpoison: fix sending SIGBUS for Action Required MCE Naoya Horiguchi
2021-04-21 0:57 ` [PATCH v3 1/3] mm/memory-failure: Use a mutex to avoid memory_failure() races Naoya Horiguchi
2021-04-22 17:01 ` Borislav Petkov
2021-04-21 0:57 ` [PATCH v3 2/3] mm,hwpoison: return -EHWPOISON when page already Naoya Horiguchi
2021-04-22 17:02 ` Borislav Petkov
2021-04-23 2:17 ` HORIGUCHI NAOYA(堀口 直也)
2021-04-21 0:57 ` [PATCH v3 3/3] mm,hwpoison: add kill_accessing_process() to find error virtual address Naoya Horiguchi
2021-04-22 17:02 ` Borislav Petkov
2021-04-23 2:18 ` HORIGUCHI NAOYA(堀口 直也)
2021-04-23 11:57 ` Borislav Petkov
2021-04-26 8:23 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-07 2:10 ` [PATCH v3 0/3] mm,hwpoison: fix sending SIGBUS for Action Required MCE Luck, Tony
2021-05-07 3:37 ` Luck, Tony
2021-05-07 5:24 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2021-05-07 11:14 ` Aili Yao
2021-05-07 18:02 ` Luck, Tony
2021-05-08 2:38 ` Aili Yao
2021-05-10 3:28 ` Luck, Tony
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=20210507052422.GB2158342@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=david@redhat.com \
--cc=juew@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=tony.luck@intel.com \
--cc=yaoaili@kingsoft.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;
as well as URLs for NNTP newsgroup(s).