From: syzbot <syzbot+ab02e4744b96de7d3499@syzkaller.appspotmail.com>
To: cem@kernel.org, hch@infradead.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] WARNING in xfs_trans_alloc
Date: Sat, 30 Aug 2025 11:03:32 -0700 [thread overview]
Message-ID: <68b33cf4.a00a0220.1337b0.0025.GAE@google.com> (raw)
In-Reply-To: <68a28720.050a0220.e29e5.0080.GAE@google.com>
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.
next prev parent reply other threads:[~2025-08-30 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 1:51 [syzbot] [xfs?] WARNING in xfs_trans_alloc syzbot
2025-08-18 4:40 ` Christoph Hellwig
2025-08-30 18:03 ` syzbot [this message]
2025-09-03 6:04 ` Christoph Hellwig
2025-09-03 6:04 ` syzbot
2025-09-03 6:05 ` Christoph Hellwig
2025-09-03 8:25 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68b33cf4.a00a0220.1337b0.0025.GAE@google.com \
--to=syzbot+ab02e4744b96de7d3499@syzkaller.appspotmail.com \
--cc=cem@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.