Re: [PATCH v2] mm/memory-failure: Support disabling soft offline for HugeTLB pages

Andrew Morton <[email protected]>
Newsgroups org.kvack.linux-mm,org.kernel.vger.linux-acpi,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest
Message-ID <[email protected]>
On Mon, 24 Aug 2026 12:53:47 -0500 Kyle Meyer <[email protected]> wrote:

> On Thu, Aug 20, 2026 at 11:47:11AM +0800, Shuai Xue wrote:
> > Hi Kyle,
> 
> Hi.
>  
> > Following up on this thread. The v2 patch once landed in akpm's mm
> > tree (9ae6eefa4b6b "mm/memory-failure: support disabling soft
> > offline for HugeTLB pages"), but that commit is now not reachable
> > from any branch, and mainline as of v7.3-rc1 still only has the 0/1
> > switch in /proc/sys/vm/enable_soft_offline.
> 
> Thanks for pointing this out.
> 
> Looks like this patch was added on 2025-09-16 [1] and dropped on 2025-11-11 [2].
> 
> [1] https://lore.kernel.org/all/[email protected]
> [2] https://lore.kernel.org/all/[email protected]
> 
> I must have missed the second email.
> 
> I don't remember discussing a v3. Can someone please remind me what we planned
> to change or whether there was another reason it was dropped?

I interpreted the (lengthy) review discussion to mean that a new
version was to be sent out.

> > The underlying issue discussed here is still unresolved for us:
> > firmware reporting per-rank corrected error thresholds via GHES
> > triggers soft offline of huge pages, which neither addresses the
> > failing rank nor is acceptable for workloads that rely on stable
> > hugetlb physical layouts.
> > 
> > Do you still plan to send a v3, e.g. with the disable-bitmask
> > layout Anshuman suggested upthread?
> 
> I wasn't planning on sending a v3 but I'm happy to revisit if needed.

That would be best at this stage - please review the changelog to see
if additional details should be added to cover the considerations which
were discussed.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.