[v6.1] WARNING in do_mknodat (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cd5d98c0556c Linux 6.1.86
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16dada35180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1002eed7bd96ee12
dashboard link: https://syzkaller.appspot.com/bug?extid=8f6fa902c365d5b882b8
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/22fd59eeffbc/disk-cd5d98c0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/064559777212/vmlinux-cd5d98c0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/11c6ce06eda3/bzImage-cd5d98c0.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88805a3571d0, owner = 0x0, curr 0xffff88807ce5bb80, list empty
WARNING: CPU: 0 PID: 4015 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 4015 at kernel/locking/rwsem.c:1372 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 4015 Comm: syz-executor.1 Not tainted 6.1.86-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/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 60 f5 eb 8a 48 c7 c6 a0 f7 eb 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 9f d5 e8 ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 a8 ab 73 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000381fd20 EFLAGS: 00010292
RAX: 9ad8fc2ef88eb400 RBX: ffffffff8aebf640 RCX: 0000000000040000
RDX: ffffc900058d9000 RSI: 0000000000015317 RDI: 0000000000015318
RBP: ffffc9000381fdf0 R08: ffffffff81528eae R09: fffff52000703f45
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff88805a3571d0 R14: 1ffff92000703fac R15: dffffc0000000000
FS: 00007feed165f6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020005038 CR3: 0000000021fb8000 CR4: 00000000003506f0
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:3929 [inline]
do_mknodat+0x44f/0x5a0 fs/namei.c:4052
__do_sys_mknodat fs/namei.c:4065 [inline]
__se_sys_mknodat fs/namei.c:4062 [inline]
__x64_sys_mknodat+0xa5/0xc0 fs/namei.c:4062
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:0x7feed087de69
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:00007feed165f0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000103
RAX: ffffffffffffffda RBX: 00007feed09ac050 RCX: 00007feed087de69
RDX: 0000000000002000 RSI: 0000000020000340 RDI: 0000000000000004
RBP: 00007feed08ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000702 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007feed09ac050 R15: 00007ffcb3750f18
</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