Re: [PATCHv2 1/2] mm/memory: Do not populate page table entries beyond i_size
From: Kiryl Shutsemau
Date: Fri Oct 24 2025 - 05:26:24 EST
On Thu, Oct 23, 2025 at 02:36:24PM -0700, Andrew Morton wrote:
> On Thu, 23 Oct 2025 22:54:49 +0200 David Hildenbrand <david@xxxxxxxxxx> wrote:
>
> > >> Fixes: 19773df031bc ("mm/fault: try to map the entire file folio in finish_fault()")
> > >
> > > Sep 28 2025
> > >
> > >> Fixes: 357b92761d94 ("mm/filemap: map entire large folio faultaround")
> > >
> > > Sep 28 2025
> > >
> > >> Fixes: 800d8c63b2e9 ("shmem: add huge pages support")
> > >
> > > Jul 26 2016
> > >
> > > eek, what's this one doing here? Are we asking -stable maintainers
> > > to backport this patch into nine years worth of kernels?
> > >
> > > I'll remove this Fixes: line for now...
> >
> > Ehm, why?
>
> Because the Sep 28 2025 Fixes: totally fooled me and because this
> doesn't apply to 6.17, let alone to 6.ancient.
>
> > It sure is a fix for that. We can indicate to which stable
> > versions we want to have ti backported.
> >
> > And yes, it might be all stable kernels.
>
> No probs, thanks for clarifying. I'll restore the
>
> Fixes: 800d8c63b2e9 ("shmem: add huge pages support")
> Cc; <stable@xxxxxxxxxxxxxxx>
>
> and shall let others sort out the backporting issues.
One possible way to relax backporting requirements is only to backport
to kernels where we can have writable file mapping to filesystem with a
backing storage (non-shmem).
Maybe
Fixes: 01c70267053d ("fs: add a filesystem flag for THPs")
--
Kiryl Shutsemau / Kirill A. Shutemov