[v5.15] WARNING in reiserfs_lookup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7349e40704a0 Linux 5.15.116
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1459b027280000
kernel config: https://syzkaller.appspot.com/x/.config?x=831c3122ac9c9145
dashboard link: https://syzkaller.appspot.com/bug?extid=569132600788c08ce33e
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8c03c3ad4501/disk-7349e407.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/350c3d79bc87/vmlinux-7349e407.xz
kernel image: https://storage.googleapis.com/syzbot-assets/73a4ed3d5438/bzImage-7349e407.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+569132...@syzkaller.appspotmail.com

loop4: detected capacity change from 0 to 32768
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 1 PID: 30190 at kernel/locking/mutex.c:575 __mutex_lock_common+0x1a52/0x25a0 kernel/locking/mutex.c:575
Modules linked in:
CPU: 1 PID: 30190 Comm: syz-executor.4 Not tainted 5.15.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:__mutex_lock_common+0x1a52/0x25a0 kernel/locking/mutex.c:575
Code: 04 08 84 c0 0f 85 d9 08 00 00 83 3d ff 7f c0 03 00 0f 85 e9 e6 ff ff 48 c7 c7 60 eb 8a 8a 48 c7 c6 a0 eb 8a 8a e8 9e 55 28 f7 <0f> 0b e9 cf e6 ff ff e8 b2 0f dd f6 e9 58 fb ff ff 0f 0b e9 d1 f0
RSP: 0018:ffffc90003b1f5e0 EFLAGS: 00010246
RAX: 6550b8e93d802800 RBX: dffffc0000000000 RCX: 0000000000040000
RDX: ffffc90006911000 RSI: 0000000000005b20 RDI: 0000000000005b21
RBP: ffffc90003b1f750 R08: ffffffff8166491c R09: ffffed1017364f24
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888042277828 R14: 0000000000000000 R15: 0000000000000000
FS: 00007fdfa2af4700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200bd038 CR3: 0000000027a50000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000000003b DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27
reiserfs_lookup+0x15c/0x4b0 fs/reiserfs/namei.c:364
__lookup_slow+0x275/0x3d0 fs/namei.c:1659
lookup_slow+0x53/0x70 fs/namei.c:1676
walk_component+0x48c/0x610 fs/namei.c:1972
lookup_last fs/namei.c:2427 [inline]
path_lookupat+0x16f/0x450 fs/namei.c:2451
filename_lookup+0x230/0x5c0 fs/namei.c:2480
user_path_at_empty+0x40/0x180 fs/namei.c:2853
user_path_at include/linux/namei.h:57 [inline]
__do_sys_chdir fs/open.c:490 [inline]
__se_sys_chdir+0xbb/0x220 fs/open.c:484
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fdfa4582199
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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:00007fdfa2af4168 EFLAGS: 00000246 ORIG_RAX: 0000000000000050
RAX: ffffffffffffffda RBX: 00007fdfa46a1f80 RCX: 00007fdfa4582199
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000040
RBP: 00007fdfa45ddca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff0931cc9f R14: 00007fdfa2af4300 R15: 0000000000022000
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.