From: "Luck, Tony" <tony.luck@intel.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: Naoya Horiguchi <nao.horiguchi@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: RE: [PATCH v1 2/2] mm/memory-failure: send SIGBUS(BUS_MCEERR_AR) only to current thread
Date: Tue, 9 Jun 2020 16:30:37 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F655E41@ORSMSX115.amr.corp.intel.com> (raw)
In-Reply-To: <20200609022919.GA28268@hori.linux.bs1.fc.nec.co.jp>
>> Does the new code now send SIGBUS(BUS_MCEERR_AO) to all the other threads
>> of a multi-threaded process?
>
> No, it doesn't. This patch should not change anything for Action Optional
> case, and find_early_kill_thread() chooses one thread per process, so
> SIGBUS(BUS_MCEERR_AO) (as well as SIGBUS(BUS_MCEERR_AR)) should be sent only
> to the chosen thread.
Ok. I think I see it now.
Acked-by: Tony Luck <tony.luck@intel.com>
-Tony
next prev parent reply other threads:[~2020-06-09 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:37 [PATCH v1 0/2] hwpoison: fixes signaling on memory error 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 [this message]
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(堀口 直也)
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=3908561D78D1C84285E8C5FCA982C28F7F655E41@ORSMSX115.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=naoya.horiguchi@nec.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