Re: mm.git review status at 7.2-rc7

[Matthew Wilcox <willy@infradead.org>]

On Wed, Aug 12, 2026 at 10:37:13AM +0200, David Hildenbrand (Arm) wrote:
> > We really need more maple_tree reviewers.
> > 
> >> Lorenzo Stoakes (ARM) <ljs@kernel.org> (6 total)
> >>     "mm/huge_memory: separate out CONFIG_PERSISTENT_HUGE_ZERO_FOLIO logic"
> >>         Link: https://lore.kernel.org/20260730-fix-refcounted-huge-zero-v2-2-c5d8a41b317f@kernel.org
> > 
> > I want to review that. I am still not convinced that we really need that right
> > now. The fix was the important bit.
> 
> Oh, good, we fast-tracked an unreviewed cleanup as a stable fix upstream.
> 
> What is happening.

Meanwhile a well-reviewed series which includes bugfixes is apparently
not even being considered for this merge window because I spent a lot of
time figuring out what Sashiko was concerned about?

https://lore.kernel.org/linux-mm/20260805210557.1118966-1-willy@infradead.org/

This was originally posted 5 weeks ago (ie when rc2 was current), so I
don't understand why it's not being considered.  It's been tested by the
people most likely to uncover bugs in it.  It's not going to get any
realistic testing in -next because most people use neither hugetlb nor
hwpoison.

There's a bunch more patches to come, and getting this batch in now
would be very convenient.  Otherwise it's going to balloon to 30 patches
next kernel release.