[moderation] [fs?] WARNING in lookup_slow (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ba16c1cf11c9 Merge tag 'edac_urgent_for_v6.9' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11b89220980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9d7ea7de0cb32587
dashboard link: https://syzkaller.appspot.com/bug?extid=cf57630b8fb07c398c35
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/bf33b57f5750/disk-ba16c1cf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5656c2dd228d/vmlinux-ba16c1cf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8807d572a9fd/bzImage-ba16c1cf.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(!is_rwsem_reader_owned(sem)): count = 0x1, magic = 0xffff88804bc23d58, owner = 0xffff88805d2ada00, curr 0xffff88805d2a9e00, list empty
WARNING: CPU: 1 PID: 11868 at kernel/locking/rwsem.c:1343 __up_read+0x617/0x6b0 kernel/locking/rwsem.c:1343
Modules linked in:
CPU: 1 PID: 11868 Comm: syz-executor.2 Not tainted 6.9.0-rc7-syzkaller-00188-gba16c1cf11c9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:__up_read+0x617/0x6b0 kernel/locking/rwsem.c:1343
Code: 8b 48 0f 44 c1 48 c7 c7 20 ac ca 8b 48 c7 c6 c0 ac ca 8b 4c 89 fa 4c 89 f1 49 89 d8 4d 89 e9 50 e8 8e af e6 ff 48 83 c4 08 90 <0f> 0b 90 90 48 bb 00 00 00 00 00 fc ff df 4c 8b 2c 24 e9 37 fb ff
RSP: 0018:ffffc90002e978e0 EFLAGS: 00010292
RAX: 36e0b43e895ab400 RBX: ffff88805d2ada00 RCX: 0000000000040000
RDX: ffffc9000a0bc000 RSI: 0000000000009a16 RDI: 0000000000009a17
RBP: ffffc90002e97998 R08: ffffffff81587c52 R09: 1ffffffff1f4f99d
R10: dffffc0000000000 R11: fffffbfff1f4f99e R12: ffff88804bc23db0
R13: ffff88805d2a9e00 R14: ffff88804bc23d58 R15: 0000000000000001
FS: 00007fa8439266c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa843905d58 CR3: 000000004d816000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock_shared include/linux/fs.h:810 [inline]
lookup_slow+0x5e/0x70 fs/namei.c:1710
walk_component+0x2e1/0x410 fs/namei.c:2004
lookup_last fs/namei.c:2461 [inline]
path_lookupat+0x16f/0x450 fs/namei.c:2485
filename_lookup+0x256/0x610 fs/namei.c:2514
vfs_statx+0x105/0x4e0 fs/stat.c:244
vfs_fstatat fs/stat.c:304 [inline]
vfs_lstat include/linux/fs.h:3267 [inline]
__do_sys_newlstat fs/stat.c:454 [inline]
__se_sys_newlstat fs/stat.c:448 [inline]
__x64_sys_newlstat+0xf5/0x180 fs/stat.c:448
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa842c7dd69
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:00007fa8439260c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000006
RAX: ffffffffffffffda RBX: 00007fa842dac120 RCX: 00007fa842c7dd69
RDX: 0000000000000000 RSI: 0000000020000a40 RDI: 0000000020000840
RBP: 00007fa842cca49e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fa842dac120 R15: 00007ffe94b36fb8
</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