From: Andrew Morton <akpm@linux-foundation.org>
To: Jinjiang Tu <tujinjiang@huawei.com>
Cc: <andrii@kernel.org>, <avagin@gmail.com>,
<baolin.wang@linux.alibaba.com>, <brahmajit.xyz@gmail.com>,
<catalin.marinas@arm.com>, <christophe.leroy@csgroup.eu>,
<david@redhat.com>, <dev.jain@arm.com>, <hughd@google.com>,
<joern@logfs.org>, <linux-mm@kvack.org>,
<lorenzo.stoakes@oracle.com>, <mhocko@suse.com>,
<rientjes@google.com>, <ryan.roberts@arm.com>,
<superman.xpt@gmail.com>, <thiago.bauermann@linaro.org>,
<wangkefeng.wang@huawei.com>
Subject: Re: [PATCH] mm/memory-failure: hold PTL in hwpoison_hugetlb_range
Date: Fri, 25 Jul 2025 16:29:13 -0700 [thread overview]
Message-ID: <20250725162913.5ab54fa56b8b67c749cff948@linux-foundation.org> (raw)
In-Reply-To: <20250725033112.2690158-1-tujinjiang@huawei.com>
On Fri, 25 Jul 2025 11:31:12 +0800 Jinjiang Tu <tujinjiang@huawei.com> wrote:
> Hold PTL in hwpoison_hugetlb_range() to avoid operating on stale page, as
> hwpoison_pte_range() have done.
Does this fix any known runtime issues? Or is it expected to?
In other words, do we have reason to backport this fix into earlier
kernels?
next prev parent reply other threads:[~2025-07-25 23:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 9:09 [PATCH v2 0/3] hold PTL for several .hugetlb_entry callbacks Jinjiang Tu
2025-07-24 9:09 ` [PATCH v2 1/3] mm/smaps: fix race between smaps_hugetlb_range and migration Jinjiang Tu
2025-07-24 16:27 ` David Hildenbrand
2025-07-24 9:09 ` [PATCH v2 2/3] fs/proc/task_mmu: hold PTL in pagemap_hugetlb_range and gather_hugetlb_stats Jinjiang Tu
2025-07-24 16:27 ` David Hildenbrand
2025-07-24 9:09 ` [PATCH v2 3/3] mm/mincore: hold PTL in mincore_hugetlb Jinjiang Tu
2025-07-24 16:29 ` David Hildenbrand
2025-07-24 16:26 ` [PATCH v2 0/3] hold PTL for several .hugetlb_entry callbacks David Hildenbrand
2025-07-25 2:02 ` Jinjiang Tu
2025-07-25 3:31 ` [PATCH] mm/memory-failure: hold PTL in hwpoison_hugetlb_range Jinjiang Tu
2025-07-25 15:48 ` David Hildenbrand
2025-07-25 23:29 ` Andrew Morton [this message]
2025-07-26 0:28 ` Jinjiang Tu
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=20250725162913.5ab54fa56b8b67c749cff948@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=avagin@gmail.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=brahmajit.xyz@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=joern@logfs.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=ryan.roberts@arm.com \
--cc=superman.xpt@gmail.com \
--cc=thiago.bauermann@linaro.org \
--cc=tujinjiang@huawei.com \
--cc=wangkefeng.wang@huawei.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