[v5.15] WARNING in lookup_slow (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 12952a23a5da Linux 5.15.137
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=162985a0e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fec74236cf840914
dashboard link: https://syzkaller.appspot.com/bug?extid=4bcc91886c98fcf15ea1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0102e80bd83/disk-12952a23.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ad4bb1832eb8/vmlinux-12952a23.xz
kernel image: https://storage.googleapis.com/syzbot-assets/530bbc85fac0/bzImage-12952a23.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(!is_rwsem_reader_owned(sem)): count = 0x0, magic = 0xffff888037bb20b0, owner = 0x0, curr 0xffff8880735d3b80, list empty
WARNING: CPU: 1 PID: 21016 at kernel/locking/rwsem.c:1315 __up_read+0x5fe/0x690 kernel/locking/rwsem.c:1315
Modules linked in:
CPU: 0 PID: 21016 Comm: syz-executor.1 Not tainted 5.15.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:__up_read+0x5fe/0x690 kernel/locking/rwsem.c:1315
Code: 8b 8a 48 0f 44 c1 48 c7 c7 60 ff 8a 8a 48 c7 c6 00 00 8b 8a 4c 89 fa 4c 89 f1 49 89 d8 4d 89 e9 50 e8 06 19 ea ff 48 83 c4 08 <0f> 0b 48 bb 00 00 00 00 00 fc ff df 4c 8b 2c 24 e9 4e fb ff ff 48
RSP: 0018:ffffc9000332f9a0 EFLAGS: 00010296
RAX: 4fe5a93736439d00 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000e0db000 RSI: 000000000000da47 RDI: 000000000000da48
RBP: ffffc9000332fa48 R08: ffffffff816658fc R09: fffff52000665e75
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888037bb2108
R13: ffff8880735d3b80 R14: ffff888037bb20b0 R15: 0000000000000000
FS: 00007fb4ddaa06c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3074a000 CR3: 0000000015ff7000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock_shared include/linux/fs.h:802 [inline]
lookup_slow+0x5e/0x70 fs/namei.c:1677
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]
path_getxattr+0xac/0x240 fs/xattr.c:727
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:0x7fb4df560ae9
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:00007fb4ddaa00c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000c0
RAX: ffffffffffffffda RBX: 00007fb4df680120 RCX: 00007fb4df560ae9
RDX: 0000000020000140 RSI: 0000000020000040 RDI: 0000000020000500
RBP: 00007fb4df5ac47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000095 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fb4df680120 R15: 00007ffde38c3bf8
</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

[syzbot]

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