[v6.1] WARNING in do_mkdirat (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0cbb5f65e52f Linux 6.1.128
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fd07df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc2b829869bb5b0
dashboard link: https://syzkaller.appspot.com/bug?extid=36262c2b9a30c332218c
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/680f32f28c80/disk-0cbb5f65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/514603ef9a94/vmlinux-0cbb5f65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f89226271f05/bzImage-0cbb5f65.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff8880558a0a90, owner = 0x0, curr 0xffff88802b6b0000, list empty
WARNING: CPU: 1 PID: 5985 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 5985 at kernel/locking/rwsem.c:1372 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 5985 Comm: syz.2.424 Not tainted 6.1.128-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1371 [inline]
RIP: 0010:up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Code: 48 c7 c7 a0 10 0c 8b 48 c7 c6 e0 12 0c 8b 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 6f ba e8 ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 78 c1 a0 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90005f5fd40 EFLAGS: 00010292
RAX: e2bca183d7f04700 RBX: ffffffff8b0c1180 RCX: 0000000000080000
RDX: ffffc9000e80a000 RSI: 000000000001f350 RDI: 000000000001f351
RBP: ffffc90005f5fe10 R08: ffffffff8152adbe R09: fffff52000bebf09
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff8880558a0a90 R14: 1ffff92000bebfb0 R15: dffffc0000000000
FS: 00007f5a600016c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c249f3f CR3: 000000006296d000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:763 [inline]
done_path_create fs/namei.c:3927 [inline]
do_mkdirat+0x278/0x360 fs/namei.c:4134
__do_sys_mkdirat fs/namei.c:4146 [inline]
__se_sys_mkdirat fs/namei.c:4144 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4144
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f5a5f18b657
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 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:00007f5a60000e68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f5a60000ef0 RCX: 00007f5a5f18b657
RDX: 00000000000001ff RSI: 0000400000000680 RDI: 00000000ffffff9c
RBP: 0000400000000080 R08: 0000400000000140 R09: 0000000000000000
R10: 0000400000000080 R11: 0000000000000246 R12: 0000400000000680
R13: 00007f5a60000eb0 R14: 0000000000000000 R15: 0000000000000000
</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.