On Sun, 25 Oct 2026 10:52:29 +0800 Muchun Song <[email protected]> wrote:
> > your series "mm: Unify device DAX and HugeTLB vmemmap population paths"
> > exposes it. That's
> >
> > 4b77739fe789 ("mm/sparse-vmemmap: drop VMEMMAP_POPULATE_DAX").
> >
> > I intend to send this to Linus next week.
> >
> > Maybe also a Fixes: 4b77739fe789. That series didn't create the bug,
> > but this data provides notification to people who are backporting this
> > series (unlikely) "hey, you need to add this fix as well".
>
> Based on the above info, do you think it is necessary to include this
> commit as a Fixes tag? My inclination is to exclude it, because the
> issue is still there. It's just that it gets triggered earlier when the
> debug kernel is enabled.
OK, skip that. This patch "dax/bus: Fix Device DAX range alignment
validation v5" has cc:stable anyway so things will work out.
