[moderation] [xfs?] invalid opcode in xfs_inodegc_worker

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 09fbf3d50205 Merge tag 'tomoyo-pr-20250211' of git://git.c..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=159889b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c516b1c112a81e77
dashboard link: https://syzkaller.appspot.com/bug?extid=5a74ee399d45a349afa9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [c...@kernel.org 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/f952dd0d3577/disk-09fbf3d5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/15b571b9069e/vmlinux-09fbf3d5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/299fb2913d4e/bzImage-09fbf3d5.xz

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

Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 5922 Comm: kworker/1:6 Not tainted 6.14.0-rc2-syzkaller-00039-g09fbf3d50205 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: xfs-inodegc/loop3 xfs_inodegc_worker
RIP: 0010:xfs_inodegc_worker+0x2/0x810 fs/xfs/xfs_icache.c:1948
Code: 5d 41 5e 41 5f 5d e9 4d f5 ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f <1e> fa 55 41 57 41 56 41 55 41 54 53 48 83 ec 28 49 89 ff 48 bb 00
RSP: 0000:ffffc90004a4fb18 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff88802dd82018 RCX: 1ffff11005bb0403
RDX: 0000000000000000 RSI: ffffffff8c5fb8e0 RDI: ffffe8ffffd67b68
RBP: ffffc90004a4fd20 R08: ffffffff8188d315 R09: 1ffffffff20346ce
R10: dffffc0000000000 R11: ffffffff837da4f2 R12: ffffe8ffffd67b68
R13: ffffffff8188d286 R14: 0000000000000001 R15: 0000000001800000
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9b11e93000 CR3: 000000007a18e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work kernel/workqueue.c:3236 [inline]
process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317
worker_thread+0x870/0xd30 kernel/workqueue.c:3398
kthread+0x7a9/0x920 kernel/kthread.c:464
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:xfs_inodegc_worker+0x2/0x810 fs/xfs/xfs_icache.c:1948
Code: 5d 41 5e 41 5f 5d e9 4d f5 ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f <1e> fa 55 41 57 41 56 41 55 41 54 53 48 83 ec 28 49 89 ff 48 bb 00
RSP: 0000:ffffc90004a4fb18 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff88802dd82018 RCX: 1ffff11005bb0403
RDX: 0000000000000000 RSI: ffffffff8c5fb8e0 RDI: ffffe8ffffd67b68
RBP: ffffc90004a4fd20 R08: ffffffff8188d315 R09: 1ffffffff20346ce
R10: dffffc0000000000 R11: ffffffff837da4f2 R12: ffffe8ffffd67b68
R13: ffffffff8188d286 R14: 0000000000000001 R15: 0000000001800000
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe825b70220 CR3: 0000000034d76000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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