mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Noah Feldt <noah@feldt.systems>
Cc: Shakeel Butt <shakeel.butt@linux.dev>,
	Johannes Weiner <hannes@cmpxchg.org>,
	David Hildenbrand <david@kernel.org>,
	Qi Zheng <qi.zheng@linux.dev>, Kairui Song <kasong@tencent.com>,
	Barry Song <baohua@kernel.org>,
	Meta kernel team <kernel-team@meta.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] mm: mglru: splice all generations when reparenting a memcg
Date: Sun, 15 Nov 2026 06:54:02 -0800	[thread overview]
Message-ID: <20261115065402.90457052d92ddf668f7e37d5@linux-foundation.org> (raw)
In-Reply-To: <20261115124954.7146-1-noah@feldt.systems>

On Sun, 15 Nov 2026 12:50:02 +0000 Noah Feldt <noah@feldt.systems> wrote:

> On Wed, Nov 11, 2026, Shakeel Butt wrote:
> > Noah reported list_del corruption on single-node hosts running 7.2.11,
> > which already has commit bf4ade7dbd76 ("memcg: keep folio's objcg same
> > as its node"). The bad pointer is an MGLRU list head in a freed
> > mem_cgroup_per_node:
> 
> I have already rolled this patch out on our servers. Since then the
> panics and resulting restarts from my report have stopped, and we have
> not noticed any other unusual behaviour.
> 
> Tested-by: Noah Feldt <noah@feldt.systems>

Great, thanks, added to changelog.

This patch is in the mm-hotfixes queue for upstreaming during this -rc
cycle.  It has cc:stable.


      reply	other threads:[~2026-11-15 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  0:09 Shakeel Butt
2026-11-11  0:27 ` Barry Song
2026-11-11  8:57   ` Kairui Song
2026-11-11 18:13 ` Kairui Song
2026-11-12  8:46   ` Baolin Wang
2026-11-15 12:50 ` Noah Feldt
2026-11-15 14:54   ` Andrew Morton [this message]

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=20261115065402.90457052d92ddf668f7e37d5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kasong@tencent.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=noah@feldt.systems \
    --cc=qi.zheng@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=stable@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®