[moderation] [fs?] WARNING in vfs_setxattr (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b5d2afe8745b Merge branches 'for-next/kbuild', 'for-next/m..
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=1679b5b3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=560f5db1d0b3f6d0
dashboard link: https://syzkaller.appspot.com/bug?extid=d308ec620170b6ca7672
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/50bff35e1638/disk-b5d2afe8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4eeaa73e7ed1/vmlinux-b5d2afe8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8e796b089aa9/Image-b5d2afe8.gz.xz

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

WARNING: CPU: 0 PID: 8194 at kernel/locking/rwsem.c:1370 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 0 PID: 8194 at kernel/locking/rwsem.c:1370 up_write+0x524/0x760 kernel/locking/rwsem.c:1632
Modules linked in:
CPU: 0 PID: 8194 Comm: syz-executor.3 Not tainted 6.9.0-rc3-syzkaller-gb5d2afe8745b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/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 : ffff8000a0837880
x29: ffff8000a0837900 x28: 0000000000000000 x27: 1fffe0001e92ce70
x26: dfff800000000000 x25: 1fffe0001e92ce64 x24: ffff0000f4967370
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000ec515ac0
x20: ffff0000f4967318 x19: ffff0000f4967318 x18: 1fffe000367b9996
x17: ffff80008ee7d000 x16: ffff800080333fec x15: 0000000000000001
x14: 1fffe000367bc590 x13: 0000000000000000 x12: 0000000000000003
x11: 0000000000000001 x10: 0000000000000003 x9 : 33fab10b2f91d800
x8 : 33fab10b2f91d800 x7 : ffff8000802aabc8 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80008afdfb40 x0 : ffff800124ffb000
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:800 [inline]
vfs_setxattr+0x1b4/0x344 fs/xattr.c:323
do_setxattr fs/xattr.c:629 [inline]
setxattr+0x208/0x29c fs/xattr.c:652
path_setxattr+0x17c/0x258 fs/xattr.c:671
__do_sys_setxattr fs/xattr.c:687 [inline]
__se_sys_setxattr fs/xattr.c:683 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:683
__invoke_syscall arch/arm64/kernel/syscall.c:34 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152
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: 278
hardirqs last enabled at (277): [<ffff8000802aac68>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1397 [inline]
hardirqs last enabled at (277): [<ffff8000802aac68>] finish_lock_switch+0xbc/0x1e4 kernel/sched/core.c:5163
hardirqs last disabled at (278): [<ffff80008ae6c78c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:470
softirqs last enabled at (270): [<ffff8000800218e4>] softirq_handle_end kernel/softirq.c:400 [inline]
softirqs last enabled at (270): [<ffff8000800218e4>] __do_softirq+0xb10/0xd2c kernel/softirq.c:583
softirqs last disabled at (231): [<ffff80008002ad34>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:81
---[ 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