From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Tony Luck <tony.luck@intel.com>, wetp <wetp.zy@linux.alibaba.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>
Subject: Re: [PATCH v1 0/2] hwpoison: fixes signaling on memory error
Date: Mon, 8 Jun 2020 02:25:48 +0000 [thread overview]
Message-ID: <20200608022547.GA2671@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20200607175318.3143676881eba60454726059@linux-foundation.org>
On Sun, Jun 07, 2020 at 05:53:18PM -0700, Andrew Morton wrote:
> On Fri, 5 Jun 2020 01:46:46 +0000 HORIGUCHI NAOYA(堀口 直也) <naoya.horiguchi@nec.com> wrote:
>
> > Sorry, recipients are not enough. I meant to send/CC this to reviewers.
> >
> > https://lore.kernel.org/linux-mm/1591321039-22141-1-git-send-email-naoya.horiguchi@nec.com/T/#t
> >
> > Any comment is welcomed.
>
> How serious are these issues? Do you think serious enough to justify
> adding these to 5.8?
The issue of 1/2 is not serious. But the issue of 2/2 is a little severer,
where we could wrongly kill the main thread when the subthread access to
the error in multithread applications. So I want it to be merged for 5.8.
Thanks,
Naoya Horiguchi
prev parent reply other threads:[~2020-06-08 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:37 Naoya Horiguchi
2020-06-05 1:37 ` [PATCH v1 1/2] mm/memory-failure: prioritize prctl(PR_MCE_KILL) over vm.memory_failure_early_kill Naoya Horiguchi
2020-06-05 1:37 ` [PATCH v1 2/2] mm/memory-failure: send SIGBUS(BUS_MCEERR_AR) only to current thread Naoya Horiguchi
2020-06-08 22:17 ` Luck, Tony
2020-06-09 2:29 ` HORIGUCHI NAOYA(堀口 直也)
2020-06-09 16:30 ` Luck, Tony
2020-06-09 20:54 ` Pankaj Gupta
2020-06-05 1:46 ` [PATCH v1 0/2] hwpoison: fixes signaling on memory error HORIGUCHI NAOYA(堀口 直也)
2020-06-08 0:53 ` Andrew Morton
2020-06-08 2:25 ` 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=20200608022547.GA2671@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=tony.luck@intel.com \
--cc=wetp.zy@linux.alibaba.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