From: "Luck, Tony" <tony.luck@intel.com>
To: "Aili Yao" <yaoaili@kingsoft.com>,
"HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: Naoya Horiguchi <nao.horiguchi@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
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>,
"yaoaili126@gmail.com" <yaoaili126@gmail.com>
Subject: RE: [PATCH v3 0/3] mm,hwpoison: fix sending SIGBUS for Action Required MCE
Date: Fri, 7 May 2021 18:02:13 +0000 [thread overview]
Message-ID: <e6577ace06ca4ce9bbfb8195d7a2bfb7@intel.com> (raw)
In-Reply-To: <20210507191400.6258dee6@alex-virtual-machine>
> Before cc:stable, would you please do one stress test first?
> It failed in my server, but I didn't dig into it, maybe the fail is meaningless.
> Just a small suggestion.
Upstream plus these three patches passed an overnight 8-hour stress test
on four machines here (running a test that's been failing with hung kernels
and kernel crashes w/o these patches).
What were the symptoms of your failed server?
-Tony
next prev parent reply other threads:[~2021-05-07 18:02 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(堀口 直也)
2021-05-07 11:14 ` Aili Yao
2021-05-07 18:02 ` Luck, Tony [this message]
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=e6577ace06ca4ce9bbfb8195d7a2bfb7@intel.com \
--to=tony.luck@intel.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=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=yaoaili126@gmail.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).