From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+7d60b33a8a546263da7c@syzkaller.appspotmail.com>
Cc: Liam.Howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ljs@kernel.org, shakeel.butt@linux.dev,
surenb@google.com, syzkaller-bugs@googlegroups.com,
vbabka@kernel.org, Muchun Song <songmuchun@bytedance.com>,
Qi Zheng <zhengqi.arch@bytedance.com>
Subject: Re: [syzbot] [mm?] WARNING: bad unlock balance in do_wp_page
Date: Sun, 26 Apr 2026 03:49:38 -0700 [thread overview]
Message-ID: <20260426034938.db29d74982a8eb8463f8cf3a@linux-foundation.org> (raw)
In-Reply-To: <69edca15.170a0220.38e3f1.0000.GAE@google.com>
On Sun, 26 Apr 2026 01:17:25 -0700 syzbot <syzbot+7d60b33a8a546263da7c@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 6596a02b2078 Merge tag 'drm-next-2026-04-22' of https://gi..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12483702580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=24c8da4692f901cb
> dashboard link: https://syzkaller.appspot.com/bug?extid=7d60b33a8a546263da7c
> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> userspace arch: i386
>
> Unfortunately, I don't have any reproducer for this issue yet.
argh, that dreaded sentence.
Thanks.
Something's definitely amiss. This is at least the fifth report of
rcu_read_lock() imbalance post-7.0. Others:
https://lore.kernel.org/69eab803.a00a0220.17a17.004a.GAE@google.com
https://lore.kernel.org/69eab803.a00a0220.17a17.004b.GAE@google.com
https://lore.kernel.org/69eafb0e.a00a0220.9259.0031.GAE@google.com
https://lore.kernel.org/69ebcbe2.a00a0220.7773.0005.GAE@google.com
In some cases we released it too often, in other cases we failed to
release it.
The first one is slightly more useful in that it tells us that the
not-released rcu_read_lock() was taken in folio_lruvec_lock_irqsave().
Muchun & Qi: you played with that rcu locking in 31b54a5e8916. Can you
please double-check that we didn't miss something?
next prev parent reply other threads:[~2026-04-26 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 8:17 [syzbot] [mm?] WARNING: bad unlock balance in do_wp_page syzbot
2026-04-26 10:49 ` Andrew Morton [this message]
2026-04-26 15:57 ` Qi Zheng
2026-04-26 17:55 ` Andrew Morton
2026-04-27 7:24 ` Qi Zheng
2026-04-27 9:43 ` Qi Zheng
2026-04-27 10:44 ` Andrew Morton
2026-04-27 10:57 ` Qi Zheng
2026-04-27 10:43 ` Andrew Morton
2026-04-27 10:54 ` Qi Zheng
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=20260426034938.db29d74982a8eb8463f8cf3a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=syzbot+7d60b33a8a546263da7c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox