[v6.1] WARNING in do_mknodat

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4a61839152cc Linux 6.1.61
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e3a54b680000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d7ceb6c3a6b2259
dashboard link: https://syzkaller.appspot.com/bug?extid=94c2ecf49cd6ef99867d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9e3f27655b35/disk-4a618391.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/96a132a7aff9/vmlinux-4a618391.xz
kernel image: https://storage.googleapis.com/syzbot-assets/89ed7864c57a/Image-4a618391.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff00011f3b91f0, owner = 0x0, curr 0xffff0000c6f28000, list empty
WARNING: CPU: 0 PID: 6028 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 6028 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 6028 Comm: syz-executor.5 Not tainted 6.1.61-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1371 [inline]
pc : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1371 [inline]
lr : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
sp : ffff80001f247b60
x29: ffff80001f247be0 x28: ffff000121c645e0 x27: 1fffe00023e7724b
x26: dfff800000000000 x25: 1fffe00023e7723f x24: ffff00011f3b9248
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000c6f28000
x20: ffff00011f3b91f0 x19: ffff00011f3b91f0 x18: 1fffe000368ac776
x17: ffff80001580d000 x16: ffff8000083062e0 x15: ffff0001b4563bbc
x14: 1ffff00002b020b0 x13: dfff800000000000 x12: 0000000000000003
x11: ff8080000aad6948 x10: 0000000000000003 x9 : 374c74a044cfe500
x8 : 374c74a044cfe500 x7 : ffff80000827db78 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80001228c340 x0 : ffff80019ee02000
Call trace:
__up_write kernel/locking/rwsem.c:1371 [inline]
up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:761 [inline]
done_path_create fs/namei.c:3858 [inline]
do_mknodat+0x43c/0x530 fs/namei.c:3981
__do_sys_mknodat fs/namei.c:3994 [inline]
__se_sys_mknodat fs/namei.c:3991 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:3991
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 1404
hardirqs last enabled at (1403): [<ffff80000827dc18>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1366 [inline]
hardirqs last enabled at (1403): [<ffff80000827dc18>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5000
hardirqs last disabled at (1404): [<ffff800012131e54>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (1396): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (1396): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (1285): [<ffff80000802a99c>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
---[ end trace 0000000000000000 ]---


---
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.