From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Deepanshu Kartikey <kartikey406@gmail.com>,
syzbot <syzbot+079a3b213add54dd18a7@syzkaller.appspotmail.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@kernel.org, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, syzkaller-bugs@googlegroups.com,
Muchun Song <muchun.song@linux.dev>,
Minchan Kim <minchan@kernel.org>, Kairui Song <ryncsn@gmail.com>
Subject: Re: [syzbot] [cgroups?] [mm?] WARNING in memcg1_swapout
Date: Wed, 21 Jan 2026 08:35:26 -0800 [thread overview]
Message-ID: <20260121083526.81996ffd70ff4efc8484fd4d@linux-foundation.org> (raw)
In-Reply-To: <aXDponX2AQoACOaI@cmpxchg.org>
On Wed, 21 Jan 2026 09:58:42 -0500 Johannes Weiner <hannes@cmpxchg.org> wrote:
> > > I tested with the latest linux-next in sysbot. It is working fine
> >
> > Great, thanks. But we still don't have review for this one.
>
> IOW, this is not necessary anymore. Kairui's (cc'd) fix which you
> picked up fixed the syzbot reported problem.
>
> > For some reason I don't have cc:stable on this - could people
> > make a recommendation?
>
> So this:
>
> > From: Deepanshu Kartikey <kartikey406@gmail.com>
> > Subject: mm/swap_cgroup: fix kernel BUG in swap_cgroup_record
>
> can be dropped.
>
OK, thanks, I'll drop Deepanshu's "mm/swap_cgroup: fix kernel BUG in
swap_cgroup_record". I understand that Kairui's
mm-swap-use-swap-cache-as-the-swap-in-synchronize-layer-fix
(https://lkml.kernel.org/r/CAMgjq7CGUnzOVG7uSaYjzw9wD7w2dSKOHprJfaEp4CcGLgE3iw@mail.gmail.com)
has addressed this mm-unstable issue.
However Deepanshu's "mm/swap_cgroup: fix kernel BUG in
swap_cgroup_record" has
Fixes: 1a4e58cce84e ("mm: introduce MADV_PAGEOUT")
Which I assume was mistaken?
next prev parent reply other threads:[~2026-01-21 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 9:30 syzbot
2026-01-18 0:57 ` Andrew Morton
2026-01-18 4:21 ` Deepanshu Kartikey
2026-01-18 7:01 ` Deepanshu Kartikey
2026-01-18 20:53 ` Andrew Morton
2026-01-20 21:20 ` Shakeel Butt
2026-01-21 14:58 ` Johannes Weiner
2026-01-21 16:35 ` Andrew Morton [this message]
2026-01-21 17:01 ` Johannes Weiner
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=20260121083526.81996ffd70ff4efc8484fd4d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=ryncsn@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=syzbot+079a3b213add54dd18a7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox