[moderation] [xfs?] BUG: spinlock bad magic in xlog_cil_force_seq

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2ccbdf43d5e7 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17702bfe980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c79815c08cc14227
dashboard link: https://syzkaller.appspot.com/bug?extid=558be620125ec55f47f2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [chanda...@oracle.com djw...@kernel.org linux-...@vger.kernel.org linu...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9fb20954c51e/disk-2ccbdf43.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/06d78b3cf960/vmlinux-2ccbdf43.xz
kernel image: https://storage.googleapis.com/syzbot-assets/15e5b0a8df77/bzImage-2ccbdf43.xz

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

XFS (loop4): Unmounting Filesystem bfdc47fc-10d8-4eed-a562-11a831b3f791
BUG: spinlock bad magic on CPU#1, syz-executor.4/15713
lock: 0xffff8880558bf000, .magic: ffff8880, .owner: ` ʋ����` ʋ������ɋ����� /6947, .owner_cpu: 771112072
CPU: 1 PID: 15713 Comm: syz-executor.4 Not tainted 6.10.0-rc3-syzkaller-00044-g2ccbdf43d5e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline]
do_raw_spin_lock+0x209/0x370 kernel/locking/spinlock_debug.c:115
__queue_work+0x6e5/0xee0
queue_work_on+0x1c2/0x380 kernel/workqueue.c:2410
queue_work include/linux/workqueue.h:621 [inline]
xlog_cil_push_now fs/xfs/xfs_log_cil.c:1501 [inline]
xlog_cil_force_seq+0x365/0x8d0 fs/xfs/xfs_log_cil.c:1679
xfs_log_force_seq+0x1a7/0x450 fs/xfs/xfs_log.c:3368
__xfs_trans_commit+0xb98/0x1290 fs/xfs/xfs_trans.c:1029
xfs_sync_sb+0x2af/0x310 fs/xfs/libxfs/xfs_sb.c:1080
xfs_log_cover fs/xfs/xfs_log.c:1266 [inline]
xfs_log_quiesce+0x2c3/0x5b0 fs/xfs/xfs_log.c:1075
xfs_log_clean+0xa4/0xc40 fs/xfs/xfs_log.c:1082
xfs_log_unmount+0x2c/0x1c0 fs/xfs/xfs_log.c:1097
xfs_unmountfs+0x18b/0x230 fs/xfs/xfs_mount.c:1120
xfs_fs_put_super+0x65/0x150 fs/xfs/xfs_super.c:1145
generic_shutdown_super+0x136/0x2d0 fs/super.c:642
kill_block_super+0x44/0x90 fs/super.c:1676
xfs_kill_sb+0x15/0x50 fs/xfs/xfs_super.c:2045
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1267
task_work_run+0x24f/0x310 kernel/task_work.c:180
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xa27/0x27e0 kernel/exit.c:874
do_group_exit+0x207/0x2c0 kernel/exit.c:1023
get_signal+0x16a1/0x1740 kernel/signal.c:2909
arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xc9/0x370 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc6ee27e62a
Code: Unable to access opcode bytes at 0x7fc6ee27e600.
RSP: 002b:00007fc6ef08cef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: 0000000000000000 RBX: 00007fc6ef08cf80 RCX: 00007fc6ee27e62a
RDX: 0000000020009600 RSI: 0000000020009640 RDI: 00007fc6ef08cf40
RBP: 0000000020009600 R08: 00007fc6ef08cf80 R09: 0000000000200800
R10: 0000000000200800 R11: 0000000000000202 R12: 0000000020009640
R13: 00007fc6ef08cf40 R14: 0000000000009606 R15: 0000000020001340
</TASK>
------------[ cut here ]------------
UBSAN: array-index-out-of-bounds in kernel/locking/qspinlock.c:131:9
index 2887 is out of range for type 'unsigned long[8]'
CPU: 1 PID: 15713 Comm: syz-executor.4 Not tainted 6.10.0-rc3-syzkaller-00044-g2ccbdf43d5e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
ubsan_epilogue lib/ubsan.c:231 [inline]
__ubsan_handle_out_of_bounds+0x121/0x150 lib/ubsan.c:429
decode_tail kernel/locking/qspinlock.c:131 [inline]
__pv_queued_spin_lock_slowpath+0xd5a/0xdc0 kernel/locking/qspinlock.c:468
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:584 [inline]
queued_spin_lock_slowpath+0x42/0x50 arch/x86/include/asm/qspinlock.h:51
queued_spin_lock include/asm-generic/qspinlock.h:114 [inline]
do_raw_spin_lock+0x272/0x370 kernel/locking/spinlock_debug.c:116
__queue_work+0x6e5/0xee0
queue_work_on+0x1c2/0x380 kernel/workqueue.c:2410
queue_work include/linux/workqueue.h:621 [inline]
xlog_cil_push_now fs/xfs/xfs_log_cil.c:1501 [inline]
xlog_cil_force_seq+0x365/0x8d0 fs/xfs/xfs_log_cil.c:1679
xfs_log_force_seq+0x1a7/0x450 fs/xfs/xfs_log.c:3368
__xfs_trans_commit+0xb98/0x1290 fs/xfs/xfs_trans.c:1029
xfs_sync_sb+0x2af/0x310 fs/xfs/libxfs/xfs_sb.c:1080
xfs_log_cover fs/xfs/xfs_log.c:1266 [inline]
xfs_log_quiesce+0x2c3/0x5b0 fs/xfs/xfs_log.c:1075
xfs_log_clean+0xa4/0xc40 fs/xfs/xfs_log.c:1082
xfs_log_unmount+0x2c/0x1c0 fs/xfs/xfs_log.c:1097
xfs_unmountfs+0x18b/0x230 fs/xfs/xfs_mount.c:1120
xfs_fs_put_super+0x65/0x150 fs/xfs/xfs_super.c:1145
generic_shutdown_super+0x136/0x2d0 fs/super.c:642
kill_block_super+0x44/0x90 fs/super.c:1676
xfs_kill_sb+0x15/0x50 fs/xfs/xfs_super.c:2045
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1267
task_work_run+0x24f/0x310 kernel/task_work.c:180
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xa27/0x27e0 kernel/exit.c:874
do_group_exit+0x207/0x2c0 kernel/exit.c:1023
get_signal+0x16a1/0x1740 kernel/signal.c:2909
arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xc9/0x370 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc6ee27e62a
Code: Unable to access opcode bytes at 0x7fc6ee27e600.
RSP: 002b:00007fc6ef08cef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: 0000000000000000 RBX: 00007fc6ef08cf80 RCX: 00007fc6ee27e62a
RDX: 0000000020009600 RSI: 0000000020009640 RDI: 00007fc6ef08cf40
RBP: 0000000020009600 R08: 00007fc6ef08cf80 R09: 0000000000200800
R10: 0000000000200800 R11: 0000000000000202 R12: 0000000020009640
R13: 00007fc6ef08cf40 R14: 0000000000009606 R15: 0000000020001340
</TASK>
---[ end trace ]---


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