[syzbot] [xfs?] WARNING in xfs_trans_alloc

[syzbot] [xfs?] WARNING in xfs_trans_alloc

[syzbot]

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

Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc

[Christoph Hellwig]

This should be fixed by:

https://web.git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/commit/?h=for-next&id=647b3d59c768d7638dd17c78c8044178364383ca

which just went into mainline.

Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit:    8f5ae30d69d7 Linux 6.17-rc1
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=15474242580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8c5ac3d8b8abfcb
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
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10891a62580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14a32a62580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/18a2e4bd0c4a/disk-8f5ae30d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b5395881b25/vmlinux-8f5ae30d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e875f4e3b7ff/Image-8f5ae30d.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f4f2ae1e66f9/mount_3.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=12458e34580000)

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: 1 PID: 24 at fs/xfs/xfs_trans.c:256 xfs_trans_alloc+0x3e4/0x898 fs/xfs/xfs_trans.c:256
Modules linked in:
CPU: 1 UID: 0 PID: 24 Comm: kworker/1:0 Not tainted 6.17.0-rc1-syzkaller-g8f5ae30d69d7 #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
Workqueue: xfs-inodegc/loop0 xfs_inodegc_worker
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : xfs_trans_alloc+0x3e4/0x898 fs/xfs/xfs_trans.c:256
lr : xfs_trans_alloc+0x3e4/0x898 fs/xfs/xfs_trans.c:256
sp : ffff800097ce77e0
x29: ffff800097ce7860 x28: ffff0000c2490130 x27: 0000000000000000
x26: ffff0000c2490000 x25: dfff800000000000 x24: 1ffff00012f9cf18
x23: dfff800000000000 x22: ffff0000c249043c x21: ffff0000c2490440
x20: ffff0000c2490438 x19: 0000000000000004 x18: 1fffe000337a0688
x17: ffff800093507000 x16: ffff80008b007230 x15: 0000000000000001
x14: 1fffe0001e61bbb5 x13: 0000000000000000 x12: 0000000000000000
x11: ffff60001e61bbb6 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000c1ae8000 x7 : ffff800081e80e40 x6 : 0000000000000000
x5 : ffff800097ce78e0 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000004 x0 : 0000000000000004
Call trace:
 xfs_trans_alloc+0x3e4/0x898 fs/xfs/xfs_trans.c:256 (P)
 xfs_attr_inactive+0xec/0x2b0 fs/xfs/xfs_attr_inactive.c:343
 xfs_inactive+0x7ac/0xb74 fs/xfs/xfs_inode.c:1464
 xfs_inodegc_inactivate fs/xfs/xfs_icache.c:1944 [inline]
 xfs_inodegc_worker+0x320/0x83c fs/xfs/xfs_icache.c:1990
 process_one_work+0x7e8/0x155c kernel/workqueue.c:3236
 process_scheduled_works kernel/workqueue.c:3319 [inline]
 worker_thread+0x958/0xed8 kernel/workqueue.c:3400
 kthread+0x5fc/0x75c kernel/kthread.c:463
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844
irq event stamp: 1049032
hardirqs last  enabled at (1049031): [<ffff80008b028e88>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
hardirqs last  enabled at (1049031): [<ffff80008b028e88>] _raw_spin_unlock_irq+0x30/0x80 kernel/locking/spinlock.c:202
hardirqs last disabled at (1049032): [<ffff80008b001bfc>] el1_brk64+0x1c/0x48 arch/arm64/kernel/entry-common.c:574
softirqs last  enabled at (1048974): [<ffff8000803d88a0>] softirq_handle_end kernel/softirq.c:425 [inline]
softirqs last  enabled at (1048974): [<ffff8000803d88a0>] handle_softirqs+0xaf8/0xc88 kernel/softirq.c:607
softirqs last disabled at (1048959): [<ffff800080022028>] __do_softirq+0x14/0x20 kernel/softirq.c:613
---[ end trace 0000000000000000 ]---


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc

[Christoph Hellwig]

#syz test v6.17-rc4

Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc

[syzbot]

> #syz test v6.17-rc4

want either no args or 2 args (repo, branch), got 1

>

Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc

[Christoph Hellwig]

#syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc

[syzbot]

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+ab02e4744b96de7d3499@syzkaller.appspotmail.com
Tested-by: syzbot+ab02e4744b96de7d3499@syzkaller.appspotmail.com

Tested on:

commit:         e6b9dce0 Merge tag 'sound-6.17-rc5' of git://git.kerne..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145aee62580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=39f8a155475bc42d
dashboard link: https://syzkaller.appspot.com/bug?extid=ab02e4744b96de7d3499
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.