Re: [PATCH 5.15 00/91] 5.15.108-rc1 review

From: Yu Zhao
Date: Thu Apr 20 2023 - 02:48:08 EST


On Wed, Apr 19, 2023 at 9:09 AM Tom Saeger <tom.saeger@xxxxxxxxxx> wrote:
>
> On Tue, Apr 18, 2023 at 10:56:22PM -0600, Yu Zhao wrote:
> > On Tue, Apr 18, 2023 at 10:18 PM Bagas Sanjaya <bagasdotme@xxxxxxxxx> wrote:
> > >
> > > On Tue, Apr 18, 2023 at 10:51:05AM -0600, Tom Saeger wrote:
> > > > > Tom Saeger identified that the below commit moves it out of ifdef.
> > > > >
> > > > > commit 354ed597442952fb680c9cafc7e4eb8a76f9514c
> > > > > Author: Yu Zhao <yuzhao@xxxxxxxxxx>
> > > > > Date: Sun Sep 18 02:00:07 2022 -0600
> > > > >
> > > > > mm: multi-gen LRU: kill switch
> > > > >
> > > > FWIW - partially backporting (location of cgroup_mutex extern) from:
> > > > 354ed5974429 ("mm: multi-gen LRU: kill switch")
> > > >
> > > > fixes x86_64 build for me.
> > > >
> > > > Regards,
> > > >
> > > > --Tom
> > > >
> > > > diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
> >
> > ...
> >
> > > Yu, would you like to provide formal backport?
>
> Nah - an easier fix was suggested by Waiman (remove the lockdep_assert_held line) and confirmed here:
>
> https://lore.kernel.org/stable/20230418192807.n3hggjak25tnat7i@xxxxxxxxxx/
>
> >
> > Are you suggesting backporting the entire MGLRU patchset (>30 patches)?
> >
> > I do have the backport ready for 5.15 and multiple distros have taken
> > it.
>
> However, I am interested in testing 5.15 backport of MGLRU.
> Where might I find that?

git://github.com/yuzhaogoogle/linux mglru-5.15