From: jane.chu@oracle.com
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: linux-mm@kvack.org, stable@vger.kernel.org,
muchun.song@linux.dev, osalvador@suse.de, david@kernel.org,
jiaqiyan@google.com, william.roche@oracle.com,
rientjes@google.com, akpm@linux-foundation.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@Oracle.com,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
willy@infradead.org, clm@meta.com,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 2/2] mm/memory-failure: teach kill_accessing_process to accept hugetlb tail page pfn
Date: Thu, 15 Jan 2026 10:17:38 -0800 [thread overview]
Message-ID: <cd880ec7-b433-4534-ac1e-4c5af4bea462@oracle.com> (raw)
In-Reply-To: <d925a432-2773-3a02-6bf6-99a2e5e83727@huawei.com>
On 1/14/2026 11:36 PM, Miaohe Lin wrote:
> On 2026/1/15 5:37, Jane Chu wrote:
>> When a hugetlb folio is being poisoned again, try_memory_failure_hugetlb()
>> passed head pfn to kill_accessing_process(), that is not right.
>> The precise pfn of the poisoned page should be used in order to
>> determine the precise vaddr as the SIGBUS payload.
>>
>> This issue has already been taken care of in the normal path, that is,
>> hwpoison_user_mappings(), see [1][2]. Further more, for [3] to work
>> correctly in the hugetlb repoisoning case, it's essential to inform
>> VM the precise poisoned page, not the head page.
>>
>> [1] https://lkml.kernel.org/r/20231218135837.3310403-1-willy@infradead.org
>> [2] https://lkml.kernel.org/r/20250224211445.2663312-1-jane.chu@oracle.com
>> [3] https://lore.kernel.org/lkml/20251116013223.1557158-1-jiaqiyan@google.com/
>>
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Jane Chu <jane.chu@oracle.com>
>> Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
>> ---
>> v5, v4: No change.
>> v2 -> v3:
>> incorporated suggestions from Miaohe and Matthew.
>> v1 -> v2:
>> pickup R-B, add stable to cc list.
>> ---
>> mm/memory-failure.c | 14 ++++++++------
>> 1 file changed, 8 insertions(+), 6 deletions(-)
>>
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index 2563718c34c6..f6b806499caa 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -692,6 +692,8 @@ static int check_hwpoisoned_entry(pte_t pte, unsigned long addr, short shift,
>> unsigned long poisoned_pfn, struct to_kill *tk)
>> {
>> unsigned long pfn = 0;
>> + unsigned long hwpoison_vaddr;
>> + unsigned long mask;
>>
>> if (pte_present(pte)) {
>> pfn = pte_pfn(pte);
>> @@ -702,10 +704,12 @@ static int check_hwpoisoned_entry(pte_t pte, unsigned long addr, short shift,
>> pfn = softleaf_to_pfn(entry);
>> }
>>
>> - if (!pfn || pfn != poisoned_pfn)
>> + mask = ~((1UL << (shift - PAGE_SHIFT)) - 1);
>> + if (!pfn || ((pfn & mask) != (poisoned_pfn & mask)))
>> return 0;
>
> Nit: Maybe "(!pfn || pfn != (poisoned_pfn & mask))" is enough?
That's nicer.
>
> Acked-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks!
-jane
>
> Thanks.
> .
>
next prev parent reply other threads:[~2026-01-15 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 21:37 [PATCH v5 1/2] mm/memory-failure: fix missing ->mf_stats count in hugetlb poison Jane Chu
2026-01-14 21:37 ` [PATCH v5 2/2] mm/memory-failure: teach kill_accessing_process to accept hugetlb tail page pfn Jane Chu
2026-01-15 7:36 ` Miaohe Lin
2026-01-15 18:17 ` jane.chu [this message]
2026-01-15 7:31 ` [PATCH v5 1/2] mm/memory-failure: fix missing ->mf_stats count in hugetlb poison Miaohe Lin
2026-01-15 18:16 ` jane.chu
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=cd880ec7-b433-4534-ac1e-4c5af4bea462@oracle.com \
--to=jane.chu@oracle.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=clm@meta.com \
--cc=david@kernel.org \
--cc=jiaqiyan@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=william.roche@oracle.com \
--cc=willy@infradead.org \
/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