[v6.1] WARNING in do_renameat2

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 779f9571ac3e Linux 6.1.164
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16eeb55a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link: https://syzkaller.appspot.com/bug?extid=61e4de7e938149e6d8f8
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/85e761437fc4/disk-779f9571.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0f3aa7ae77ae/vmlinux-779f9571.xz
kernel image: https://storage.googleapis.com/syzbot-assets/baba59a67bd9/Image-779f9571.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000fd1fa0b0, owner = 0x0, curr 0xffff0000ce0e0000, list empty
WARNING: CPU: 0 PID: 7180 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 7180 at kernel/locking/rwsem.c:1372 up_write+0x494/0x5bc kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 7180 Comm: syz.8.876 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
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 : ffff800024337b00
x29: ffff800024337b10 x28: ffff0000f58c85e0 x27: 0000000000000000
x26: dfff800000000000 x25: 1fffe0001fa3f423 x24: ffff0000fd1fa108
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000ce0e0000
x20: ffff0000fd1fa0b0 x19: ffff0000fd1fa0b0 x18: ffff800011b8bf60
x17: 0000000000000000 x16: ffff8000082d9364 x15: 0000000000000002
x14: 0000000000000001 x13: 1fffe00033ea87a3 x12: 0000000000080000
x11: 000000000000cfed x10: ffff800025dcc000 x9 : 8b5474881fefa800
x8 : 8b5474881fefa800 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800024337598 x4 : ffff8000152f4cc0 x3 : ffff800008538704
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000000
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 fs/namei.c:3095 [inline]
do_renameat2+0x788/0xa74 fs/namei.c:5041
__do_sys_renameat2 fs/namei.c:5068 [inline]
__se_sys_renameat2 fs/namei.c:5065 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5065
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b4 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: 224
hardirqs last enabled at (223): [<ffff80000830fb6c>] __up_console_sem+0xb4/0xfc kernel/printk/printk.c:261
hardirqs last disabled at (224): [<ffff800011a22ed4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (144): [<ffff800008030954>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (142): [<ffff800008030920>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ 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