From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+12ee2725d5fde63a9c96@syzkaller.appspotmail.com>,
axelrasmussen@google.com, baohua@kernel.org,
baolin.wang@linux.alibaba.com, cgroups@vger.kernel.org,
david@kernel.org, hannes@cmpxchg.org, kasong@tencent.com,
kernel-team@meta.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ljs@kernel.org, mhocko@kernel.org,
mhocko@suse.com, muchun.song@linux.dev, qi.zheng@linux.dev,
roman.gushchin@linux.dev, syzkaller-bugs@googlegroups.com,
weixugc@google.com, yuanchu@google.com
Subject: Re: [syzbot] [mm?] WARNING in set_mm_walk
Date: Wed, 12 Aug 2026 14:41:49 -0700 [thread overview]
Message-ID: <anzojtrifviGUjLN@linux.dev> (raw)
In-Reply-To: <20260812140358.343927ad8d0955b67c4e7ad5@linux-foundation.org>
On Wed, Aug 12, 2026 at 02:03:58PM -0700, Andrew Morton wrote:
> On Wed, 12 Aug 2026 05:26:24 -0700 syzbot <syzbot+12ee2725d5fde63a9c96@syzkaller.appspotmail.com> wrote:
>
> > syzbot has found a reproducer for the following issue on:
> >
> > HEAD commit: f5bbbfec59b4 Merge tag 'probes-fixes-v7.2-rc7' of git://gi..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=11f44c79580000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
> > dashboard link: https://syzkaller.appspot.com/bug?extid=12ee2725d5fde63a9c96
> > compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d11149580000
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+12ee2725d5fde63a9c96@syzkaller.appspotmail.com
> >
> > ------------[ cut here ]------------
> > current_is_kswapd()
> > WARNING: mm/vmscan.c:3800 at set_mm_walk+0x210/0x270 mm/vmscan.c:3800, CPU#2: kswapd0/111
>
> Thanks. Shakeel is working on a series which will fix this by removing
> the calling code. But it isn't a minor patch.
>
> Shakeel, it would be good to have a backportable quick-fix to make this
> warning go away?
>
Actually the first patch [1] of the series will fix this warning and we can
backport just that patch to the older stable kernels.
Do you want me to send that patch as a standalone?
[1] https://lore.kernel.org/all/20260811203203.3456029-2-shakeel.butt@linux.dev/
prev parent reply other threads:[~2026-08-12 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a7a6929.b50370da.49fe0.005e.GAE@google.com>
2026-08-12 12:26 ` [syzbot] [mm?] WARNING in set_mm_walk syzbot
2026-08-12 21:03 ` Andrew Morton
2026-08-12 21:41 ` Shakeel Butt [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=anzojtrifviGUjLN@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=cgroups@vger.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=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=qi.zheng@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=syzbot+12ee2725d5fde63a9c96@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox