[moderation] [fs?] WARNING: locking bug in lookup_slow

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1f719a2f3fa6 Merge tag 'net-6.8-rc4' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11a94120180000
kernel config: https://syzkaller.appspot.com/x/.config?x=89a5d896b14c4565
dashboard link: https://syzkaller.appspot.com/bug?extid=026c18dc370027b54487
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/25164a45d43e/disk-1f719a2f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/040d61123d29/vmlinux-1f719a2f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5027d3f8d940/bzImage-1f719a2f.xz

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

------------[ cut here ]------------
Looking for class "&inode->i_rwsem" with key lockdep_annotate_inode_mutex_key.__key, but found a different class "&sb->s_type->i_mutex_key" with the same key
WARNING: CPU: 0 PID: 7180 at kernel/locking/lockdep.c:935 look_up_lock_class+0xdc/0x160 kernel/locking/lockdep.c:932
Modules linked in:
CPU: 0 PID: 7180 Comm: syz-executor.0 Not tainted 6.8.0-rc3-syzkaller-00136-g1f719a2f3fa6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:look_up_lock_class+0xdc/0x160 kernel/locking/lockdep.c:932
Code: 01 0f 85 80 00 00 00 c6 05 55 48 11 04 01 90 49 8b 16 49 8b 76 18 48 8b 8b b8 00 00 00 48 c7 c7 80 d6 aa 8b e8 c5 d2 f9 f5 90 <0f> 0b 90 90 eb 57 90 e8 58 9e 35 f9 48 c7 c7 c0 d5 aa 8b 89 de e8
RSP: 0018:ffffc9001308f490 EFLAGS: 00010046

RAX: e30a4395ad10d100 RBX: ffffffff929a9548 RCX: 0000000000040000
RDX: ffffc90004c22000 RSI: 000000000000765f RDI: 0000000000007660
RBP: ffffc9001308f5a0 R08: ffffffff815778a2 R09: 1ffff110172851a2
R10: dffffc0000000000 R11: ffffed10172851a3 R12: ffff88803520e380
R13: ffff88803520e380 R14: ffff88803520e380 R15: ffffffff8e4bb198
FS: 00007f10d432b6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f149a2a2000 CR3: 00000000251aa000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
register_lock_class+0x102/0x980 kernel/locking/lockdep.c:1284
__lock_acquire+0xd9/0x1fd0 kernel/locking/lockdep.c:5014
lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526
inode_lock_shared include/linux/fs.h:812 [inline]
lookup_slow+0x45/0x70 fs/namei.c:1709
walk_component+0x2e1/0x410 fs/namei.c:2001
lookup_last fs/namei.c:2458 [inline]
path_lookupat+0x16f/0x450 fs/namei.c:2482
filename_lookup+0x255/0x610 fs/namei.c:2511
vfs_statx+0x105/0x4e0 fs/stat.c:244
vfs_fstatat+0x135/0x190 fs/stat.c:304
__do_sys_newfstatat fs/stat.c:468 [inline]
__se_sys_newfstatat fs/stat.c:462 [inline]
__x64_sys_newfstatat+0x117/0x190 fs/stat.c:462
do_syscall_64+0xf9/0x240
entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7f10d367dda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f10d432b0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000106
RAX: ffffffffffffffda RBX: 00007f10d37ac050 RCX: 00007f10d367dda9
RDX: 0000000000000000 RSI: 0000000020001340 RDI: ffffffffffffff9c
RBP: 00007f10d36ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f10d37ac050 R15: 00007ffc6f0a6968
</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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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