From: Jane Chu <jane.chu@oracle.com>
To: Miaohe Lin <linmiaohe@huawei.com>,
nao.horiguchi@gmail.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm/memory-failure: send SIGBUS in the event of thp split fail
Date: Wed, 8 May 2024 09:56:12 -0700 [thread overview]
Message-ID: <56448498-96e4-4350-a915-15b97294bc62@oracle.com> (raw)
In-Reply-To: <2e51deff-24ca-32d5-dbd2-9077f860723c@huawei.com>
On 5/8/2024 2:03 AM, Miaohe Lin wrote:
> On 2024/5/2 7:24, Jane Chu wrote:
>> When handle hwpoison in a GUP longterm pin'ed thp page,
>> try_to_split_thp_page() will fail. And at this point, there is little else
>> the kernel could do except sending a SIGBUS to the user process, thus
>> give it a chance to recover.
> It seems the user process will still receive SIGBUS via kill_accessing_process()
> when (re-)access thp later. So they should have a chance to recover already.
> Or am I miss something?
The concern is about real UE consumption in which case, it's desirable
to kill the process ASAP without having to relying on subsequent
access. Also to honor processes' MCE-early-kill request.
kill_accessing_process() is very conservative in that, it doesn't check
other processes that have the poisoned page mapped.
thanks,
-jane
>
> Thanks.
> .
>
>
next prev parent reply other threads:[~2024-05-08 16:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 23:24 [PATCH 0/3] Enhance soft hwpoison handling and injection Jane Chu
2024-05-01 23:24 ` [PATCH 1/3] mm/memory-failure: try to send SIGBUS even if unmap failed Jane Chu
2024-05-07 9:02 ` Oscar Salvador
2024-05-07 17:54 ` Jane Chu
2024-05-08 12:06 ` Oscar Salvador
2024-05-08 16:51 ` Jane Chu
2024-05-08 7:47 ` Miaohe Lin
2024-05-08 16:58 ` Jane Chu
2024-05-09 2:54 ` Miaohe Lin
2024-05-09 16:40 ` Jane Chu
2024-05-01 23:24 ` [PATCH 2/3] mm/madvise: Add MF_ACTION_REQUIRED to madvise(MADV_HWPOISON) Jane Chu
2024-05-05 7:02 ` Miaohe Lin
2024-05-06 19:54 ` Jane Chu
2024-05-08 7:58 ` Miaohe Lin
2024-05-01 23:24 ` [PATCH 3/3] mm/memory-failure: send SIGBUS in the event of thp split fail Jane Chu
2024-05-05 7:00 ` Miaohe Lin
2024-05-06 20:26 ` Jane Chu
2024-05-08 8:08 ` Miaohe Lin
2024-05-08 17:45 ` Jane Chu
2024-05-09 8:30 ` Miaohe Lin
2024-05-09 15:34 ` Jane Chu
2024-05-10 2:59 ` Miaohe Lin
2024-05-10 3:18 ` Jane Chu
2024-05-08 9:03 ` Miaohe Lin
2024-05-08 16:56 ` Jane Chu [this message]
2024-05-09 8:52 ` 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=56448498-96e4-4350-a915-15b97294bc62@oracle.com \
--to=jane.chu@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.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