On Thu, 18 Apr 2024 11:19:33 +0200 Vlastimil Babka <vbabka@xxxxxxx> wrote: > On 4/18/24 08:57, Christoph Hellwig wrote: > > On Thu, Apr 18, 2024 at 02:39:19AM +0100, Matthew Wilcox wrote: > >>> Running compaction while we run fsstress can crash older kernels as per > >>> korg#218227 [0], the fix for that [0] has been posted [1] but that patch > >>> is not yet on v6.9-rc4 and the patch requires changes for v6.9. > >> > >> It doesn't require changes, it just has prerequisites: > >> > >> https://lore.kernel.org/all/ZgHhcojXc9QjynUI@xxxxxxxxxxxxxxxxxxxx/ > > > > How can we expedite getting this fix in? > > It means moving patches 2,4,5 from the above (with their fixups) from > mm-unstable to mm-hotfixes-unstable so they are on track to mainline > before 6.9. > > A quick local rebase of mm-unstable with reordering said patches to the > front (v6.9-rc4) suggests this is possible without causing conflicts, > and the intermediate result compiles, at least. Thanks for the reminder, this fell through cracks. It indeed appears that I can move mm-create-folio_flag_false-and-folio_type_ops-macros.patch mm-support-page_mapcount-on-page_has_type-pages.patch mm-turn-folio_test_hugetlb-into-a-pagetype.patch mm-turn-folio_test_hugetlb-into-a-pagetype-fix.patch without merge or build issues. I added Fixes: 9c5ccf2db04b ("mm: remove HUGETLB_PAGE_DTOR") Cc: <stable@xxxxxxxxxxxxxxx> to all patches. But a question: 9c5ccf2db04b is from August 2023. Why are we seeing this issue now?
