[v5.15] WARNING in vfs_removexattr

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 284087d4f7d5 Linux 5.15.158
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13ad2248980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab74f93e8454887c
dashboard link: https://syzkaller.appspot.com/bug?extid=5f33a163aba67ef276fc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0accc7dacf9d/disk-284087d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb6b5b110f8c/vmlinux-284087d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6763bebdbfea/Image-284087d4.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000e8877930, owner = 0x0, curr 0xffff0000cce7b680, list empty
WARNING: CPU: 0 PID: 5286 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 0 PID: 5286 at kernel/locking/rwsem.c:1350 up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 0 PID: 5286 Comm: syz-executor.2 Not tainted 5.15.158-syzkaller #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:1349 [inline]
pc : up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
lr : __up_write kernel/locking/rwsem.c:1349 [inline]
lr : up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
sp : ffff80001e9b79a0
x29: ffff80001e9b79b0 x28: 1ffff00003d36f48 x27: dfff800000000000
x26: dfff800000000000 x25: 1fffe0001d10ef33 x24: ffff0000e8877988
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000cce7b680
x20: ffff0000e8877930 x19: ffff0000e8877930 x18: 0000000000000001
x17: 0000000000000002 x16: ffff800011998e34 x15: 00000000ffffffff
x14: ffff0000cce7b680 x13: 0000000000000001 x12: 0000000000040000
x11: 0000000000007612 x10: ffff80001de09000 x9 : a618c4efe3aab000
x8 : a618c4efe3aab000 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001e9b7118 x4 : ffff800014a1f7a0 x3 : ffff8000085501f8
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 00000000000000bd
Call trace:
__up_write kernel/locking/rwsem.c:1349 [inline]
up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
inode_unlock include/linux/fs.h:794 [inline]
vfs_removexattr+0xec/0x23c fs/xattr.c:529
removexattr fs/xattr.c:857 [inline]
path_removexattr+0x1ec/0x2ec fs/xattr.c:871
__do_sys_removexattr fs/xattr.c:885 [inline]
__se_sys_removexattr fs/xattr.c:882 [inline]
__arm64_sys_removexattr+0x60/0x78 fs/xattr.c:882
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 104
hardirqs last enabled at (103): [<ffff80000832b458>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (104): [<ffff8000119944c0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (8): [<ffff8000080310b0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (6): [<ffff80000803107c>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace fe956d2c7b1ffe43 ]---


---
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