[moderation] [fs?] WARNING in do_mknodat (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d206a76d7d27 Linux 6.8-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b78602180000
kernel config: https://syzkaller.appspot.com/x/.config?x=8a9dc475f1caec0d
dashboard link: https://syzkaller.appspot.com/bug?extid=82c0a707f7b49f32d011
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/8030fec6be39/disk-d206a76d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b9dea2d5888f/vmlinux-d206a76d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f40f09a220d9/bzImage-d206a76d.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff8880504b3e30, owner = 0x0, curr 0xffff888025c51dc0, list empty
WARNING: CPU: 1 PID: 11114 at kernel/locking/rwsem.c:1370 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 1 PID: 11114 at kernel/locking/rwsem.c:1370 up_write+0x500/0x580 kernel/locking/rwsem.c:1632
Modules linked in:
CPU: 1 PID: 11114 Comm: syz-executor.0 Not tainted 6.8.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1369 [inline]
RIP: 0010:up_write+0x500/0x580 kernel/locking/rwsem.c:1632
Code: c7 c7 40 aa aa 8b 48 c7 c6 80 ac aa 8b 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 b5 14 e7 ff 48 83 c4 08 90 <0f> 0b 90 90 e9 6b fd ff ff 48 c7 c1 00 70 84 8f 80 e1 07 80 c1 03
RSP: 0018:ffffc90003117d20 EFLAGS: 00010292
RAX: 92fba57d25b07f00 RBX: ffffffff8baaab20 RCX: 0000000000040000
RDX: ffffc90004d79000 RSI: 000000000002ab6d RDI: 000000000002ab6e
RBP: ffffc90003117df0 R08: ffffffff815779c2 R09: 1ffff92000622ef8
R10: dffffc0000000000 R11: fffff52000622ef9 R12: 0000000000000000
R13: ffff8880504b3e30 R14: 1ffff92000622fac R15: dffffc0000000000
FS: 00007f42da29f6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005571dfb103d0 CR3: 000000007a8d4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:809 [inline]
done_path_create fs/namei.c:3946 [inline]
do_mknodat+0x4c5/0x5b0 fs/namei.c:4069
__do_sys_mknodat fs/namei.c:4082 [inline]
__se_sys_mknodat fs/namei.c:4079 [inline]
__x64_sys_mknodat+0xa9/0xc0 fs/namei.c:4079
do_syscall_64+0xf9/0x240
entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7f42d947dda9
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:00007f42da29f0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000103
RAX: ffffffffffffffda RBX: 00007f42d95ac050 RCX: 00007f42d947dda9
RDX: 0000000000000000 RSI: 00000000200004c0 RDI: 0000000000000004
RBP: 00007f42d94ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000700 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f42d95ac050 R15: 00007ffc0f082888
</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