[moderation] [fs?] WARNING in vfs_removexattr (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7c626ce4bae1 Linux 6.11-rc3
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1689cdd3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c91f83ae59feaa1f
dashboard link: https://syzkaller.appspot.com/bug?extid=ad9ca5fa6f83171e3bb9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dc1150b469cf/disk-7c626ce4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fe1fd137b037/vmlinux-7c626ce4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/93e290961a43/Image-7c626ce4.gz.xz

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

WARNING: CPU: 0 PID: 7225 at kernel/locking/rwsem.c:1370 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 0 PID: 7225 at kernel/locking/rwsem.c:1370 up_write+0x524/0x760 kernel/locking/rwsem.c:1632
Modules linked in:
CPU: 0 UID: 0 PID: 7225 Comm: syz.3.179 Not tainted 6.11.0-rc3-syzkaller-g7c626ce4bae1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1369 [inline]
pc : up_write+0x524/0x760 kernel/locking/rwsem.c:1632
lr : __up_write kernel/locking/rwsem.c:1369 [inline]
lr : up_write+0x524/0x760 kernel/locking/rwsem.c:1632
sp : ffff8000a0277960
x29: ffff8000a02779e0 x28: 1ffff0001404ef50 x27: 1fffe0001ba3e028
x26: dfff800000000000 x25: 1fffe0001ba3e01c x24: ffff0000dd1f0130
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000d7463c80
x20: ffff0000dd1f00d8 x19: ffff0000dd1f00d8 x18: ffff8000a0276e80
x17: 000000000002dfec x16: ffff800080345098 x15: 0000000000000001
x14: 1ffff00011fbbe06 x13: 0000000000000000 x12: 0000000000000003
x11: 0000000000000001 x10: 0000000000000003 x9 : 129e34befa324100
x8 : 129e34befa324100 x7 : ffff8000800603b4 x6 : ffff8000800605b0
x5 : ffff0000dba3cf20 x4 : ffff8000a02772d0 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80008b462a00 x0 : 0000000000000001
Call trace:
__up_write kernel/locking/rwsem.c:1369 [inline]
up_write+0x524/0x760 kernel/locking/rwsem.c:1632
inode_unlock include/linux/fs.h:804 [inline]
vfs_removexattr+0xec/0x23c fs/xattr.c:577
removexattr fs/xattr.c:907 [inline]
path_removexattr+0x230/0x32c fs/xattr.c:928
__do_sys_removexattr fs/xattr.c:942 [inline]
__se_sys_removexattr fs/xattr.c:939 [inline]
__arm64_sys_removexattr+0x60/0x78 fs/xattr.c:939
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598
irq event stamp: 110226
hardirqs last enabled at (110225): [<ffff800080a86974>] kasan_quarantine_put+0x1a0/0x1c8 mm/kasan/quarantine.c:234
hardirqs last disabled at (110226): [<ffff80008b2ea644>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:470
softirqs last enabled at (110116): [<ffff8000800307f8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (110114): [<ffff8000800307c4>] 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