[v5.15] WARNING in do_mknodat (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9b91d36ba301 Linux 5.15.141
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13d7be02e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a82f519bd246319
dashboard link: https://syzkaller.appspot.com/bug?extid=a1e8e01ac6964d7f0bb9
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/4b6df384a084/disk-9b91d36b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/43304db9d8de/vmlinux-9b91d36b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/04c9a4d2fc86/Image-9b91d36b.gz.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000df2c91f0, owner = 0x0, curr 0xffff0000d7dad1c0, list empty
WARNING: CPU: 0 PID: 6320 at kernel/locking/rwsem.c:1342 __up_write kernel/locking/rwsem.c:1341 [inline]
WARNING: CPU: 0 PID: 6320 at kernel/locking/rwsem.c:1342 up_write+0x384/0x438 kernel/locking/rwsem.c:1594
Modules linked in:
CPU: 0 PID: 6320 Comm: syz-executor.2 Not tainted 5.15.141-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1341 [inline]
pc : up_write+0x384/0x438 kernel/locking/rwsem.c:1594
lr : __up_write kernel/locking/rwsem.c:1341 [inline]
lr : up_write+0x384/0x438 kernel/locking/rwsem.c:1594
sp : ffff80001ecc7bc0
x29: ffff80001ecc7bd0 x28: ffff000100810000 x27: 0000000000000000
x26: dfff800000000000 x25: 1fffe0001be5924b x24: ffff0000df2c9248
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000d7dad1c0
x20: ffff0000df2c91f0 x19: ffff0000df2c91f0 x18: 1fffe000368fe78e
x17: 1fffe000368fe78e x16: ffff800011974734 x15: ffff8000149becc0
x14: 1ffff0000292406a x13: dfff800000000000 x12: 0000000000040000
x11: 00000000000199ab x10: ffff8000218ce000 x9 : fcf4363fd3fdb900
x8 : fcf4363fd3fdb900 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000a95b740
x2 : ffff0001b47f3d10 x1 : 0000000100000000 x0 : 00000000000000bd
Call trace:
__up_write kernel/locking/rwsem.c:1341 [inline]
up_write+0x384/0x438 kernel/locking/rwsem.c:1594
inode_unlock include/linux/fs.h:792 [inline]
done_path_create fs/namei.c:3815 [inline]
do_mknodat+0x410/0x674 fs/namei.c:3938
__do_sys_mknodat fs/namei.c:3951 [inline]
__se_sys_mknodat fs/namei.c:3948 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:3948
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 432
hardirqs last enabled at (431): [<ffff800008268510>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1338 [inline]
hardirqs last enabled at (431): [<ffff800008268510>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:4784
hardirqs last disabled at (432): [<ffff80001196fdc0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (426): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (426): [<ffff800008020ccc>] __do_softirq+0xb5c/0xdb0 kernel/softirq.c:587
softirqs last disabled at (317): [<ffff8000081b5568>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (317): [<ffff8000081b5568>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (317): [<ffff8000081b5568>] __irq_exit_rcu+0x264/0x4d4 kernel/softirq.c:637
---[ end trace eea5a4dd806bd238 ]---


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