[v6.1] WARNING in do_symlinkat

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59b13c2b647e Linux 6.1.52
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1501b2c8680000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f66357f6e0916fc
dashboard link: https://syzkaller.appspot.com/bug?extid=491f9582eac6729ab880
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/5d1e69df9f69/disk-59b13c2b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb34994a3de5/vmlinux-59b13c2b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/49d4e70cb0b8/Image-59b13c2b.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000d0af36d0, owner = 0x0, curr 0xffff0000ca3e1bc0, list empty
WARNING: CPU: 1 PID: 5554 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 5554 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 5554 Comm: syz-executor.1 Not tainted 6.1.52-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/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 : ffff80001e007b80
x29: ffff80001e007c00 x28: 1ffff00003c00f90 x27: 1fffe0001a15e6e7
x26: dfff800000000000 x25: 1fffe0001a15e6db x24: ffff0000d0af3728
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000ca3e1bc0
x20: ffff0000d0af36d0 x19: ffff0000d0af36d0 x18: 1fffe000368adf76
x17: ffff8000158ad000 x16: ffff800008304a94 x15: ffff0001b456fbbc
x14: 1ffff00002b160b0 x13: dfff800000000000 x12: 0000000000000003
x11: ff8080000aacd7a8 x10: 0000000000000003 x9 : 9a5a134766441a00
x8 : 9a5a134766441a00 x7 : ffff80000827c428 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80001227c340 x0 : ffff80019ed6e000
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_symlinkat+0x3b4/0x6b0 fs/namei.c:4433
__do_sys_symlinkat fs/namei.c:4447 [inline]
__se_sys_symlinkat fs/namei.c:4444 [inline]
__arm64_sys_symlinkat+0xa4/0xbc fs/namei.c:4444
__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: 926
hardirqs last enabled at (925): [<ffff80000827c4c8>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1366 [inline]
hardirqs last enabled at (925): [<ffff80000827c4c8>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5000
hardirqs last disabled at (926): [<ffff80001211f54c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (918): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (918): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (749): [<ffff80000802a994>] ____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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.