From: Jinjiang Tu <tujinjiang@huawei.com>
To: <jane.chu@oracle.com>, <linmiaohe@huawei.com>,
<nao.horiguchi@gmail.com>, <akpm@linux-foundation.org>,
<xueshuai@linux.alibaba.com>, <david@redhat.com>,
<ziy@nvidia.com>, <osalvador@suse.de>, <linux-mm@kvack.org>
Cc: <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v2] mm/memory-failure: fix infinite UCE for VM_PFNMAP'ed page
Date: Fri, 15 Aug 2025 09:16:56 +0800 [thread overview]
Message-ID: <cba9fcb9-9548-488e-a914-d88ff38dc513@huawei.com> (raw)
In-Reply-To: <1f5d5a50-2f30-4c1e-bdb2-1c0103cb5b07@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]
在 2025/8/14 14:05, jane.chu@oracle.com 写道:
>
> On 8/10/2025 9:33 PM, Jinjiang Tu wrote:
>> When memory_failure() is called for a already hwpoisoned pfn backed with
>> struct page, kill_accessing_process() will conditionally send a
>> SIGBUS to
>> the current (triggering) process if it maps the page.
>>
>> However, in case the page is not ordinarily mapped, but was mapped
>> through
>> remap_pfn_range(), kill_accessing_process() wouldn't identify it as
>> mapped
>> even though hwpoison_pte_range() would be prepared to handle it, because
>> walk_page_range() will skip VM_PFNMAP as default in walk_page_test(). As
>> a result, walk_page_range() will return 0, assuming "not mapped" and
>> SIGBUS
>> will be skipped. The user task will trigger UCE infinitely because it
>> will
>> not receive a SIGBUS on access and simply retry.
>>
>> Before commit aaf99ac2ceb7 ("mm/hwpoison: do not send SIGBUS to
>> processes
>> with recovered clean pages"), kill_accessing_process() will return
>> EFAULT.
>> For x86, the current task will be killed in kill_me_maybe().
>>
>> To fix it, add .test_walk callback for hwpoison_walk_ops to process
>> VM_PFNMAP VMAs too.
>>
>> Fixes: aaf99ac2ceb7 ("mm/hwpoison: do not send SIGBUS to processes
>> with recovered clean pages")
>> Signed-off-by: Jinjiang Tu <tujinjiang@huawei.com>
>> ---
>> Changelog since v1:
>> * update patch description, suggested by David Hildenbrand
>>
>> mm/memory-failure.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index e2e685b971bb..fa6a8f2cdebc 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -853,9 +853,16 @@ static int hwpoison_hugetlb_range(pte_t *ptep,
>> unsigned long hmask,
>> #define hwpoison_hugetlb_range NULL
>> #endif
>> +static int hwpoison_test_walk(unsigned long start, unsigned long end,
>> + struct mm_walk *walk)
>> +{
>> + return 0;
>> +}
>> +
>> static const struct mm_walk_ops hwpoison_walk_ops = {
>> .pmd_entry = hwpoison_pte_range,
>> .hugetlb_entry = hwpoison_hugetlb_range,
>> + .test_walk = hwpoison_test_walk,
>> .walk_lock = PGWALK_RDLOCK,
>> };
>
> Looks good. Could you add this to stable ?
Yes, I will.
>
> Reviewed-by: Jane Chu <jane.chu@oracle.com>
>
> thanks,
> -jane
>
>
>
[-- Attachment #2: Type: text/html, Size: 4123 bytes --]
prev parent reply other threads:[~2025-08-15 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 4:33 Jinjiang Tu
2025-08-11 7:54 ` David Hildenbrand
2025-08-12 2:01 ` Miaohe Lin
2025-08-14 6:40 ` David Hildenbrand
2025-08-15 1:16 ` Jinjiang Tu
2025-08-14 6:05 ` jane.chu
2025-08-15 1:16 ` Jinjiang Tu [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=cba9fcb9-9548-488e-a914-d88ff38dc513@huawei.com \
--to=tujinjiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jane.chu@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=wangkefeng.wang@huawei.com \
--cc=xueshuai@linux.alibaba.com \
--cc=ziy@nvidia.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