[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20241104141834.fc30ea90bbc80446d0fcf1f0@linux-foundation.org>
Date: Mon, 4 Nov 2024 14:18:34 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Yu Zhao <yuzhao@...gle.com>
Cc: Shakeel Butt <shakeel.butt@...ux.dev>, Johannes Weiner
<hannes@...xchg.org>, Michal Hocko <mhocko@...nel.org>, Roman Gushchin
<roman.gushchin@...ux.dev>, Muchun Song <muchun.song@...ux.dev>, Hugh
Dickins <hughd@...gle.com>, Yosry Ahmed <yosryahmed@...gle.com>,
linux-mm@...ck.org, cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-doc@...r.kernel.org, Meta kernel team
<kernel-team@...a.com>
Subject: Re: [PATCH v1 5/6] memcg-v1: no need for memcg locking for MGLRU
On Mon, 4 Nov 2024 15:08:09 -0700 Yu Zhao <yuzhao@...gle.com> wrote:
> > The assertion was caused by the patch in this thread. It used to
> > assert that a folio must be protected from charge migration. Charge
> > migration is removed by this series, and as part of the effort, this
> > patch removes the RCU lock.
> >
> > > And a link to the sysbot report?
> >
> > https://syzkaller.appspot.com/bug?extid=24f45b8beab9788e467e
>
> Or this link would work better:
>
> https://lore.kernel.org/lkml/67294349.050a0220.701a.0010.GAE@google.com/
Thanks, I pasted everyone's everything in there, so it will all be
accessible by the sufficiently patient.
Powered by blists - more mailing lists