From: jane.chu@oracle.com
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org, muchun.song@linux.dev, osalvador@suse.de,
david@kernel.org, linmiaohe@huawei.com, 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
Subject: Re: [PATCH v2] mm/memory-failure: teach kill_accessing_process to accept hugetlb tail page pfn
Date: Mon, 22 Dec 2025 12:30:39 -0800 [thread overview]
Message-ID: <c5629607-274e-4dc8-b759-7a04dba390c9@oracle.com> (raw)
In-Reply-To: <aUWXAGC1028jRKEY@casper.infradead.org>
On 12/19/2025 10:18 AM, Matthew Wilcox wrote:
> On Fri, Dec 19, 2025 at 10:55:16AM -0700, Jane Chu wrote:
>> 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)
>
> if we pass in huge_page_mask() instead ...
>
>> {
>> 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))
>
> ... then we can simplify this to:
>
> if (!pfn || ((pfn | mask) != (poisoned_pfn | mask))
>
>> return 0;
>> @@ -2037,6 +2038,7 @@ static int try_memory_failure_hugetlb(unsigned long pfn, int flags, int *hugetlb
>> return action_result(pfn, MF_MSG_GET_HWPOISON, MF_IGNORED);
>> }
>>
>> +
>> folio = page_folio(p);
>> folio_lock(folio);
>
> unnecessary whitespace change
Thanks! I'll incorporate the mask idea in v3.
-jane
prev parent reply other threads:[~2025-12-22 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 17:55 Jane Chu
2025-12-19 18:18 ` Matthew Wilcox
2025-12-22 20:30 ` jane.chu [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=c5629607-274e-4dc8-b759-7a04dba390c9@oracle.com \
--to=jane.chu@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--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