[v6.1] BUG: corrupted list in vfs_setxattr

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3594f306da12 Linux 6.1.147
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11db4434580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2be97b627a5d7554
dashboard link: https://syzkaller.appspot.com/bug?extid=32b4c5b10bfd4a6dce27
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0d2a884e198e/disk-3594f306.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/23d3643328c7/vmlinux-3594f306.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ef83d78711e3/Image-3594f306.gz.xz

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

list_del corruption. prev->next should be ffff800020d578a0, but was ffff0000fc45c468. (prev=ffff0000fc45c468)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 6113 Comm: syz.2.391 Not tainted 6.1.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __list_del_entry_valid+0x13c/0x158 lib/list_debug.c:59
lr : __list_del_entry_valid+0x13c/0x158 lib/list_debug.c:59
sp : ffff800020d57750
x29: ffff800020d57750 x28: ffff0000d32e3190 x27: 1fffe0001f88b892
x26: ffff0000fc45c468 x25: ffff0000d32e1bc0 x24: 0000000000000001
x23: 0000000000000000 x22: dfff800000000000 x21: ffff0000fc45c468
x20: ffff0000fc45c468 x19: ffff800020d578a0 x18: ffff800011aabce0
x17: 20747562202c3061 x16: ffff8000082e7bb0 x15: 0000000000000002
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000080000
x11: 0000000000003deb x10: ffff800029e3f000 x9 : b565984334d47700
x8 : b565984334d47700 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800020d57218 x4 : ffff800015194800 x3 : ffff80000a83eb6c
x2 : ffff00019f6efd10 x1 : 0000000100000001 x0 : 000000000000006d
Call trace:
__list_del_entry_valid+0x13c/0x158 lib/list_debug.c:59
__list_del_entry include/linux/list.h:134 [inline]
list_del include/linux/list.h:148 [inline]
rwsem_try_write_lock kernel/locking/rwsem.c:666 [inline]
rwsem_down_write_slowpath+0xc18/0x125c kernel/locking/rwsem.c:1160
__down_write_common kernel/locking/rwsem.c:1314 [inline]
__down_write kernel/locking/rwsem.c:1323 [inline]
down_write+0x84/0x88 kernel/locking/rwsem.c:1574
inode_lock include/linux/fs.h:758 [inline]
vfs_setxattr+0x138/0x2ac fs/xattr.c:308
do_setxattr fs/xattr.c:594 [inline]
setxattr+0x228/0x28c fs/xattr.c:617
path_setxattr+0x12c/0x25c fs/xattr.c:636
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648
__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
Code: 913a8000 aa1303e1 aa1503e3 95bf7d6a (d4210000)
---[ 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.