From: Shakeel Butt <shakeel.butt@linux.dev>
To: syzbot <syzbot+1a3353a77896e73a8f53@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, cgroups@vger.kernel.org,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@kernel.org, muchun.song@linux.dev,
roman.gushchin@linux.dev, syzkaller-bugs@googlegroups.com,
zhengqi.arch@bytedance.com, yosry@kernel.org
Subject: Re: [syzbot] [mm?] [cgroups?] WARNING: bad unlock balance in lruvec_stat_mod_folio
Date: Mon, 13 Apr 2026 15:28:52 -0700 [thread overview]
Message-ID: <ad1tV5WpFhxbQ86N@linux.dev> (raw)
In-Reply-To: <69d54494.050a0220.3030df.0002.GAE@google.com>
+Qi & Yosry
On Tue, Apr 07, 2026 at 10:53:24AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: cc13002a9f98 Add linux-next specific files for 20260402
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=10d8946a580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4e6c8be618ab359
> dashboard link: https://syzkaller.appspot.com/bug?extid=1a3353a77896e73a8f53
> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
>
> Unfortunately, I don't have any reproducer for this issue yet.
Let's wait for the reproducer. I can only think of cgroup_subsys_on_dfl() check
returning different value in get_non_dying_memcg_start() and
get_non_dying_memcg_end() to cause this uneven rcu unlock. However I can't think
why and how that can happen.
next prev parent reply other threads:[~2026-04-13 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 17:53 [syzbot] [mm?] [cgroups?] WARNING: bad unlock balance in lruvec_stat_mod_folio syzbot
2026-04-13 22:28 ` Shakeel Butt [this message]
2026-04-14 3:52 ` Qi Zheng
2026-04-14 17:15 ` Shakeel Butt
2026-04-15 2:22 ` Qi Zheng
2026-05-12 12:46 ` Forwarded: " syzbot
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=ad1tV5WpFhxbQ86N@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=syzbot+1a3353a77896e73a8f53@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yosry@kernel.org \
--cc=zhengqi.arch@bytedance.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.