[v6.1] WARNING in do_mkdirat

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=134534f9c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ccbc3d5467efd1
dashboard link: https://syzkaller.appspot.com/bug?extid=7cb5edea961cbeb1d497
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7fe538fc87bf/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8df93997601a/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/03ad7e3bf859/Image-543aff19.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff00012e5620b0, owner = 0x0, curr 0xffff0001360b9b40, list empty
WARNING: CPU: 1 PID: 13324 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 13324 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 13324 Comm: syz-executor.5 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/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 : ffff80001dc87b80
x29: ffff80001dc87c00 x28: 1ffff00003b90f95 x27: 1fffe00025cac423
x26: dfff800000000000 x25: 1fffe00025cac417 x24: ffff00012e562108
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0001360b9b40
x20: ffff00012e5620b0 x19: ffff00012e5620b0 x18: 1fffe000368bab76
x17: ffff80001557d000 x16: ffff8000083019d8 x15: ffff0001b45d5bbc
x14: 1ffff00002ab00b0 x13: dfff800000000000 x12: 0000000000000003
x11: ff8080000aaba988 x10: 0000000000000003 x9 : ea4af1ed37856200
x8 : ea4af1ed37856200 x7 : ffff80000827a538 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80001222c140 x0 : ffff80019f104000
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:3857 [inline]
do_mkdirat+0x258/0x610 fs/namei.c:4064
__do_sys_mkdirat fs/namei.c:4076 [inline]
__se_sys_mkdirat fs/namei.c:4074 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4074
__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:581
irq event stamp: 680
hardirqs last enabled at (679): [<ffff80000827a5d8>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1366 [inline]
hardirqs last enabled at (679): [<ffff80000827a5d8>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5000
hardirqs last disabled at (680): [<ffff8000120d75ac>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (374): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (374): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (359): [<ffff80000802a948>] ____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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.