[v6.1] WARNING in do_symlinkat (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0cbb5f65e52f Linux 6.1.128
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=133391b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=88cb0e1f997892a4
dashboard link: https://syzkaller.appspot.com/bug?extid=4c727372540aa524310a
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/acd347d0a419/disk-0cbb5f65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/08daefc52220/vmlinux-0cbb5f65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/230948781702/Image-0cbb5f65.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000e2aa7930, owner = 0x0, curr 0xffff0000cfb2b780, list empty
WARNING: CPU: 0 PID: 4864 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 4864 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 4864 Comm: syz.2.137 Not tainted 6.1.128-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
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 : ffff800021b17b80
x29: ffff800021b17c00 x28: 1ffff00004362f90 x27: 1fffe0001c554f33
x26: dfff800000000000 x25: 1fffe0001c554f27 x24: ffff0000e2aa7988
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000cfb2b780
x20: ffff0000e2aa7930 x19: ffff0000e2aa7930 x18: 1fffe0003679bf76
x17: ffff800015a8d000 x16: ffff80000830159c x15: ffff0001b3cdfbbc
x14: 1ffff00002b520b2 x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000ff0100 x10: 0000000000000003 x9 : b8d58615ac3d4500
x8 : b8d58615ac3d4500 x7 : ffff800008277b18 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80001248c5a0 x0 : ffff80019e2fc000
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:763 [inline]
done_path_create fs/namei.c:3927 [inline]
do_symlinkat+0x20c/0x45c fs/namei.c:4503
__do_sys_symlinkat fs/namei.c:4517 [inline]
__se_sys_symlinkat fs/namei.c:4514 [inline]
__arm64_sys_symlinkat+0xa4/0xbc fs/namei.c:4514
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
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: 356
hardirqs last enabled at (355): [<ffff800008277bb8>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1367 [inline]
hardirqs last enabled at (355): [<ffff800008277bb8>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5000
hardirqs last disabled at (356): [<ffff80001232d0c4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (336): [<ffff8000081c2418>] softirq_handle_end kernel/softirq.c:421 [inline]
softirqs last enabled at (336): [<ffff8000081c2418>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:606
softirqs last disabled at (247): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:612
---[ 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.