[moderation] [xfs?] Internal error in xfs_inodegc_worker

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5283dc78f4da Merge remote-tracking branch 'tip/irq/core' i..
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=161b6aa7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=46747686125c7e50
dashboard link: https://syzkaller.appspot.com/bug?extid=2ebe3aeccd6e101c94d6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
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/646a4136941e/disk-5283dc78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e985dce60177/vmlinux-5283dc78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8e09efa952c0/Image-5283dc78.gz.xz

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

Internal error: SP/PC alignment exception: 000000008a000000 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 UID: 0 PID: 27 Comm: kworker/1:1 Not tainted 6.12.0-rc5-syzkaller-g5283dc78f4da #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: xfs-inodegc/loop0 xfs_inodegc_worker
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : xfs_inodegc_worker+0x1/0x8f8 fs/xfs/xfs_icache.c:1894
lr : process_one_work+0x7bc/0x1600 kernel/workqueue.c:3229
sp : ffff8000979d7b20
x29: ffff8000979d7cb0 x28: ffff700012f3af80 x27: ffff0000c1bb9018
x26: ffff0000c1bb9010 x25: ffff0000d00ba400 x24: dfff800000000000
x23: ffff0000c1b8dac0 x22: fffffdffbf709098 x21: 0000000000000002
x20: ffff0000c1b8dec4 x19: ffff0000c1bb9000 x18: ffff8000979d7820
x17: 000000000003015f x16: ffff8000830cb3ac x15: 0000000000000001
x14: 1ffff0001264d1ac x13: dfff800000000000 x12: 0000000000000000
x11: ffff70001264d1ad x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff800081d912bd x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff80009327fc98 x4 : 0000000000000008 x3 : ffff80008035a9c8
x2 : 0000000000000001 x1 : ffff80008bb679c0 x0 : fffffdffbf709098
Call trace:
xfs_inodegc_worker+0x1/0x8f8 fs/xfs/xfs_icache.c:1894 (P)
process_one_work+0x7bc/0x1600 kernel/workqueue.c:3229 (L)
process_scheduled_works kernel/workqueue.c:3310 [inline]
worker_thread+0x97c/0xeec kernel/workqueue.c:3391
kthread+0x288/0x310 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
Code: fda9415f bfa8c47b c0d50323 3fd65f03 (ffd50323)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: fda9415f .inst 0xfda9415f ; undefined
4: bfa8c47b .inst 0xbfa8c47b ; undefined
8: c0d50323 .inst 0xc0d50323 ; undefined
c: 3fd65f03 .inst 0x3fd65f03 ; undefined
* 10: ffd50323 .inst 0xffd50323 ; undefined <-- trapping instruction


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