From: Miaohe Lin <linmiaohe@huawei.com>
To: <jane.chu@oracle.com>
Cc: <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>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/memory-failure: teach kill_accessing_process to accept hugetlb tail page pfn
Date: Mon, 22 Dec 2025 11:01:24 +0800 [thread overview]
Message-ID: <93ce8e83-500f-9f97-a90c-64d9b3c73f3a@huawei.com> (raw)
In-Reply-To: <38c098ea-95bb-476f-80c9-de9231b9c991@oracle.com>
On 2025/12/19 16:06, jane.chu@oracle.com wrote:
>
>
> On 12/19/2025 12:01 AM, Miaohe Lin wrote:
>> On 2025/12/19 14:28, 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/
>>>
>>
>> Thanks for your patch.
>>
>>> Cc: <stable@vger.kernel.org>
>>> Signed-off-by: Jane Chu <jane.chu@oracle.com>
>>> ---
>>> mm/memory-failure.c | 22 ++++++++++++----------
>>> 1 file changed, 12 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>>> index 3edebb0cda30..c9d87811b1ea 100644
>>> --- a/mm/memory-failure.c
>>> +++ b/mm/memory-failure.c
>>> @@ -681,9 +681,11 @@ static void set_to_kill(struct to_kill *tk, unsigned long addr, short shift)
>>> }
>>> static int check_hwpoisoned_entry(pte_t pte, unsigned long addr, short shift,
>>> - unsigned long poisoned_pfn, struct to_kill *tk)
>>> + unsigned long poisoned_pfn, struct to_kill *tk,
>>> + int pte_nr)
>>> {
>>> unsigned long pfn = 0;
>>> + unsigned long hwpoison_vaddr;
>>> if (pte_present(pte)) {
>>> pfn = pte_pfn(pte);
>>> @@ -694,10 +696,11 @@ static int check_hwpoisoned_entry(pte_t pte, unsigned long addr, short shift,
>>> pfn = swp_offset_pfn(swp);
>>> }
>>> - if (!pfn || pfn != poisoned_pfn)
>>> + if (!pfn || (pfn > poisoned_pfn || (pfn + pte_nr - 1) < poisoned_pfn))
>>> return 0;
>>
>> Can we get pte_nr from @shift? I.e. something like "pte_nr = 1UL << (shift - PAGE_SHIFT);"?
>
> Why? Is there any concern with using the macro pages_per_huge_page(h) ?
No, I was trying to get rid of new @pte_nr parameter. Something like below:
static int check_hwpoisoned_entry(pte_t pte, unsigned long addr, short shift,
- unsigned long poisoned_pfn, struct to_kill *tk,
- int pte_nr)
+ unsigned long poisoned_pfn, struct to_kill *tk)
{
unsigned long pfn = 0;
unsigned long hwpoison_vaddr;
+ int pte_nr;
if (pte_present(pte)) {
pfn = pte_pfn(pte);
@@ -701,7 +701,8 @@ static int check_hwpoisoned_entry(pte_t pte, unsigned long addr, short shift,
pfn = softleaf_to_pfn(entry);
}
- if (!pfn || (pfn > poisoned_pfn || (pfn + pte_nr - 1) < poisoned_pfn))
+ pte_nr = 1UL << (shift - PAGE_SHIFT);
+ if (!pfn || (pfn > poisoned_pfn || (pfn + pte_nr - 1) < poisoned_pfn))
return 0;
hwpoison_vaddr = addr + ((poisoned_pfn - pfn) << PAGE_SHIFT);
So we don't have to pass in pte_nr from all callers. But that's trivial.
Thanks.
.
next prev parent reply other threads:[~2025-12-22 3:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 6:28 Jane Chu
2025-12-19 8:01 ` Miaohe Lin
2025-12-19 8:06 ` jane.chu
2025-12-22 3:01 ` Miaohe Lin [this message]
2025-12-22 20:29 ` jane.chu
2025-12-19 17:27 ` Liam R. Howlett
2025-12-19 17:29 ` jane.chu
2025-12-20 23:13 ` Andrew Morton
2025-12-22 20:32 ` jane.chu
2025-12-23 0:36 ` jane.chu
2025-12-21 8:49 ` David Hildenbrand (Red Hat)
2025-12-22 18:42 ` 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=93ce8e83-500f-9f97-a90c-64d9b3c73f3a@huawei.com \
--to=linmiaohe@huawei.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.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=surenb@google.com \
--cc=william.roche@oracle.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