[syzbot] [xfs?] WARNING in xfs_trans_alloc

[syzbot <syzbot+ab02e4744b96de7d3499@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    dfc0f6373094 Merge tag 'erofs-for-6.17-rc2-fixes' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12bfcda2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=13f39c6a0380a209
dashboard link: https://syzkaller.appspot.com/bug?extid=ab02e4744b96de7d3499
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/471a095bde0f/disk-dfc0f637.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dfa0446324a1/vmlinux-dfc0f637.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a43829df052/bzImage-dfc0f637.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 990 at fs/xfs/xfs_trans.c:256 xfs_trans_alloc+0x4d8/0x980 fs/xfs/xfs_trans.c:256
Modules linked in:
CPU: 0 UID: 0 PID: 990 Comm: kworker/0:2 Tainted: G        W           6.17.0-rc1-syzkaller-00036-gdfc0f6373094 #0 PREEMPT_{RT,(full)} 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: xfs-inodegc/loop2 xfs_inodegc_worker
RIP: 0010:xfs_trans_alloc+0x4d8/0x980 fs/xfs/xfs_trans.c:256
Code: 89 ef e8 1b 49 fa ff 85 c0 0f 85 14 02 00 00 e8 8e 3e 57 fe b0 01 89 44 24 24 4c 8b 64 24 78 e9 f9 fb ff ff e8 79 3e 57 fe 90 <0f> 0b 90 e9 3f fc ff ff 89 d9 80 e1 07 fe c1 38 c1 0f 8c 13 fc ff
RSP: 0018:ffffc90004acf7f8 EFLAGS: 00010293
RAX: ffffffff83671cc7 RBX: 0000000000000004 RCX: ffff8880253cd940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff888053a08000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1e3a727 R12: ffff888053a08130
R13: 0000000000000000 R14: 1ffff1100a741073 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8881268c5000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff8b6a64f98 CR3: 000000002370a000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 xfs_inactive_truncate+0xa5/0x1b0 fs/xfs/xfs_inode.c:1152
 xfs_inactive+0x949/0xcd0 fs/xfs/xfs_inode.c:1454
 xfs_inodegc_inactivate fs/xfs/xfs_icache.c:1944 [inline]
 xfs_inodegc_worker+0x31e/0x7c0 fs/xfs/xfs_icache.c:1990
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3319
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>


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