From: syzbot <syzbot+0b16dd9bd622c40b2bbe@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] WARNING: bad unlock balance in traverse
Date: Wed, 26 Feb 2025 13:53:20 -0800 [thread overview]
Message-ID: <67bf8d50.050a0220.1ebef.0095.GAE@google.com> (raw)
In-Reply-To: <67bf882e.050a0220.1ebef.008f.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: ac9c34d1e45a Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=175b003f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1635bf4c5557b92
dashboard link: https://syzkaller.appspot.com/bug?extid=0b16dd9bd622c40b2bbe
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ba9db0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10479c98580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed21c75da715/disk-ac9c34d1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f51096fe566c/vmlinux-ac9c34d1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e6a27961fbbe/bzImage-ac9c34d1.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0b16dd9bd622c40b2bbe@syzkaller.appspotmail.com
RBP: 0000000000000001 R08: 00007ffd17221997 R09: 00007fd111db0032
R10: 00000000000005af R11: 0000000000000246 R12: 00007fd111db3618
R13: 00007ffd17221dd8 R14: 0000000000000001 R15: 0000000000000001
</TASK>
=====================================
WARNING: bad unlock balance detected!
6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Not tainted
-------------------------------------
syz-executor218/5831 is trying to release lock (event_mutex) at:
[<ffffffff82399e2d>] traverse.part.0.constprop.0+0x2bd/0x640 fs/seq_file.c:131
but there are no more locks to release!
other info that might help us debug this:
1 lock held by syz-executor218/5831:
#0: ffff88802f5d5790 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xd8/0x12b0 fs/seq_file.c:182
stack backtrace:
CPU: 1 UID: 0 PID: 5831 Comm: syz-executor218 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
print_unlock_imbalance_bug kernel/locking/lockdep.c:5289 [inline]
print_unlock_imbalance_bug+0x1aa/0x1f0 kernel/locking/lockdep.c:5263
__lock_release kernel/locking/lockdep.c:5528 [inline]
lock_release+0x525/0x6f0 kernel/locking/lockdep.c:5872
__mutex_unlock_slowpath+0xa3/0x6a0 kernel/locking/mutex.c:891
traverse.part.0.constprop.0+0x2bd/0x640 fs/seq_file.c:131
traverse fs/seq_file.c:98 [inline]
seq_read_iter+0x934/0x12b0 fs/seq_file.c:195
seq_read+0x39f/0x4e0 fs/seq_file.c:162
vfs_read+0x1df/0xbf0 fs/read_write.c:563
ksys_pread64 fs/read_write.c:756 [inline]
__do_sys_pread64 fs/read_write.c:764 [inline]
__se_sys_pread64 fs/read_write.c:761 [inline]
__x64_sys_pread64+0x1f6/0x250 fs/read_write.c:761
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd111d48329
Code: 48 83 c4 28 c3 e8 17 1a 00 00 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd17221bf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000011
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
prev parent reply other threads:[~2025-02-26 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 21:31 [syzbot] [fs?] WARNING: bad unlock balance in traverse syzbot
2025-02-26 21:53 ` syzbot [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=67bf8d50.050a0220.1ebef.0095.GAE@google.com \
--to=syzbot+0b16dd9bd622c40b2bbe@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.