[v6.1] WARNING in unlock_rename (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 228da13e907e Linux 6.1.175
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=125d11b6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=29caf4bae4b0566f
dashboard link: https://syzkaller.appspot.com/bug?extid=83f49f91b348211e9a25
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bf27a408696a/disk-228da13e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/264d4943ab43/vmlinux-228da13e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a499b0d2a133/Image-228da13e.gz.xz

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

WARNING: CPU: 1 PID: 6339 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 6339 at kernel/locking/rwsem.c:1372 up_write+0x494/0x5bc kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 6339 Comm: syz.2.385 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
pstate: 62400005 (nZCv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1371 [inline]
pc : up_write+0x494/0x5bc kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1371 [inline]
lr : up_write+0x494/0x5bc kernel/locking/rwsem.c:1626
sp : ffff800021597590
x29: ffff8000215975a0 x28: ffff800021597680 x27: ffff7000042b2ed0
x26: dfff800000000000 x25: 1fffe00020006c6f x24: ffff000100036368
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000ce1d3800
x20: ffff000100036310 x19: ffff000100036310 x18: ffff800011babf60
x17: 1fffe00033ea397e x16: ffff8000082d9e48 x15: 0000000040000000
x14: 0000000000000001 x13: 1fffe00033ea6030 x12: 0000000000ff0100
x11: ff0080000a8e1d70 x10: 0000000000000003 x9 : c95ba99978eea200
x8 : c95ba99978eea200 x7 : ffff800008258510 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000006 x1 : ffff800011bada80 x0 : ffff80018a387000
Call trace:
__up_write kernel/locking/rwsem.c:1371 [inline]
up_write+0x494/0x5bc kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:763 [inline]
unlock_rename+0x48/0xb8 fs/namei.c:3095
ovl_workdir_ok fs/overlayfs/super.c:984 [inline]
ovl_get_workdir+0x1e4/0x10bc fs/overlayfs/super.c:1519
ovl_fill_super+0x1390/0x2240 fs/overlayfs/super.c:2095
mount_nodev+0x68/0x104 fs/super.c:1489
ovl_mount+0x3c/0x50 fs/overlayfs/super.c:2186
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x228/0x810 fs/namespace.c:3078
path_mount+0x5bc/0xe80 fs/namespace.c:3408
do_mount fs/namespace.c:3421 [inline]
__do_sys_mount fs/namespace.c:3629 [inline]
__se_sys_mount fs/namespace.c:3606 [inline]
__arm64_sys_mount+0x49c/0x59c fs/namespace.c:3606
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 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: 470
hardirqs last enabled at (469): [<ffff8000082585a4>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1374 [inline]
hardirqs last enabled at (469): [<ffff8000082585a4>] finish_lock_switch+0xb0/0x1c4 kernel/sched/core.c:5004
hardirqs last disabled at (470): [<ffff800011a4ebe4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (462): [<ffff8000081acd08>] softirq_handle_end kernel/softirq.c:439 [inline]
softirqs last enabled at (462): [<ffff8000081acd08>] handle_softirqs+0xaec/0xc60 kernel/softirq.c:624
softirqs last disabled at (313): [<ffff800008020e4c>] __do_softirq+0x14/0x20 kernel/softirq.c:630
---[ 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