[moderation] [fs?] WARNING in do_rmdir

Hello,

syzbot found the following issue on:

HEAD commit: c62f4b82d571 Merge tag 'v6.15-p4' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a6e470580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a972ee73c2fcf8ca
dashboard link: https://syzkaller.appspot.com/bug?extid=5137233e6c55b3fe89dd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [[email protected] [email protected] [email protected] [email protected] [email protected]]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-c62f4b82.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1408b7d32b67/vmlinux-c62f4b82.xz
kernel image: https://storage.googleapis.com/syzbot-assets/27dead5a4082/bzImage-c62f4b82.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888044704e38, owner = 0x0, curr 0xffff888000a0a440, list empty
WARNING: CPU: 0 PID: 5326 at kernel/locking/rwsem.c:1368 __up_write kernel/locking/rwsem.c:1367 [inline]
WARNING: CPU: 0 PID: 5326 at kernel/locking/rwsem.c:1368 up_write+0x506/0x590 kernel/locking/rwsem.c:1630
Modules linked in:
CPU: 0 UID: 0 PID: 5326 Comm: syz.0.0 Not tainted 6.15.0-rc2-syzkaller-00048-gc62f4b82d571 #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:__up_write kernel/locking/rwsem.c:1367 [inline]
RIP: 0010:up_write+0x506/0x590 kernel/locking/rwsem.c:1630
Code: c7 c7 20 db 4a 8c 48 c7 c6 40 dd 4a 8c 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 ff 0a e4 ff 48 83 c4 08 90 <0f> 0b 90 90 e9 6a fd ff ff 48 c7 c1 64 10 60 90 80 e1 07 80 c1 03
RSP: 0018:ffffc9000d677d00 EFLAGS: 00010296
RAX: 1d51bcddc2a7da00 RBX: ffffffff8c4adc00 RCX: ffff888000a0a440
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000d677dd0 R08: ffffffff81827952 R09: 1ffff11003f847d2
R10: dffffc0000000000 R11: ffffed1003f847d3 R12: 0000000000000000
R13: ffff888044704e38 R14: 1ffff92001acefa8 R15: dffffc0000000000
FS: 00007f60bce2f6c0(0000) GS:ffff88808c593000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd967a3f40 CR3: 0000000043da0000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:872 [inline]
do_rmdir+0x3dd/0x550 fs/namei.c:4478
__do_sys_rmdir fs/namei.c:4493 [inline]
__se_sys_rmdir fs/namei.c:4491 [inline]
__x64_sys_rmdir+0x47/0x50 fs/namei.c:4491
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f60bbf8e169
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f60bce2f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 00007f60bc1b6160 RCX: 00007f60bbf8e169
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000100
RBP: 00007f60bc010a68 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f60bc1b6160 R15: 00007ffd967a4928
</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 [email protected].

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