From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Karl Erik Hofseth <karl.e.hofseth@opoint.com>,
linux-mm@kvack.org, qi.zheng@linux.dev, kasong@tencent.com,
baohua@kernel.org, axelrasmussen@google.com, yuanchu@google.com,
weixugc@google.com, hannes@cmpxchg.org, mhocko@kernel.org,
roman.gushchin@linux.dev, muchun.song@linux.dev,
david@kernel.org, ljs@kernel.org, cgroups@vger.kernel.org,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] mm/memcg: folio/lruvec mismatch after cgroup offline: lru_size underflow and list_del corruption (7.1)
Date: Wed, 5 Aug 2026 10:22:45 -0700 [thread overview]
Message-ID: <anNxSMBgNeLytWOu@linux.dev> (raw)
In-Reply-To: <20260805093522.e3ba46aca3a143207d68a65e@linux-foundation.org>
On Wed, Aug 05, 2026 at 09:35:22AM -0700, Andrew Morton wrote:
> On Wed, 05 Aug 2026 14:03:03 +0200 (CEST) Karl Erik Hofseth <karl.e.hofseth@opoint.com> wrote:
>
> > The following KASAN slab-use-after-free comes from a Fedora debug kernel
> > build of 7.1.6 with de4660898b7a applied on top, provoked with the
> > attached script. Further down are OOPSes generated by workloads in
> > production on stock Fedora kernels. MGLRU on/off makes no difference.
>
> Thanks. It does appear to be a race between migration and memcg
> removal.
>
> Gemini provides some thoughts, although I've found these AI crash
> interpretations to be a bit unreliable.
>
> https://share.gemini.google/Y6dMvOlHIFuV
I am looking into the issue and will report back.
next prev parent reply other threads:[~2026-08-05 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 12:03 [REGRESSION] mm/memcg: folio/lruvec mismatch after cgroup offline: lru_size underflow and list_del corruption (7.1) Karl Erik Hofseth
2026-08-05 16:35 ` Andrew Morton
2026-08-05 17:22 ` Shakeel Butt [this message]
2026-08-05 19:07 ` Shakeel Butt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=anNxSMBgNeLytWOu@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=karl.e.hofseth@opoint.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=qi.zheng@linux.dev \
--cc=regressions@lists.linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.