[v6.1] WARNING in chown_common (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 50cbba13faa2 Linux 6.1.159
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17161e22580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31ea1cecaf34f0db
dashboard link: https://syzkaller.appspot.com/bug?extid=ac66e799fe4c2c027fc4
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.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/7ad0bd66715a/disk-50cbba13.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3284d626258e/vmlinux-50cbba13.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a1f92ca7bbfc/Image-50cbba13.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000e22d1bc0, owner = 0x0, curr 0xffff0000f8770000, list empty
WARNING: CPU: 0 PID: 6165 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 6165 at kernel/locking/rwsem.c:1372 up_write+0x494/0x5c0 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 6165 Comm: syz.3.585 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/0x5c0 kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1371 [inline]
lr : up_write+0x494/0x5c0 kernel/locking/rwsem.c:1626
sp : ffff800020a27aa0
x29: ffff800020a27ab0 x28: 0000000000000000 x27: ffff8000150d3cc0
x26: dfff800000000000 x25: 1fffe0001c45a385 x24: ffff0000e22d1c18
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000f8770000
x20: ffff0000e22d1bc0 x19: ffff0000e22d1bc0 x18: ffff800011a5bd40
x17: 1fffe00033ee7b7e x16: ffff8000082d3a08 x15: 0000000040000000
x14: 0000000000000002 x13: 1ffff00002a0a0b1 x12: 0000000000ff0100
x11: ff0080000a895d54 x10: 0000000000000003 x9 : e1c8634d444a9a00
x8 : e1c8634d444a9a00 x7 : ffff8000082532dc x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff800011a5d840 x0 : ffff80018a798000
Call trace:
__up_write kernel/locking/rwsem.c:1371 [inline]
up_write+0x494/0x5c0 kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:763 [inline]
chown_common+0x420/0x574 fs/open.c:738
do_fchownat+0x158/0x268 fs/open.c:767
__do_sys_fchownat fs/open.c:782 [inline]
__se_sys_fchownat fs/open.c:779 [inline]
__arm64_sys_fchownat+0xb8/0xd4 fs/open.c:779
__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/0x138 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: 154
hardirqs last enabled at (153): [<ffff800008253370>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1367 [inline]
hardirqs last enabled at (153): [<ffff800008253370>] finish_lock_switch+0xb0/0x1c4 kernel/sched/core.c:5003
hardirqs last disabled at (154): [<ffff8000118fa220>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (8): [<ffff8000080309e0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (6): [<ffff8000080309ac>] 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