[syzbot] Monthly xfs report (Oct 2025)

0 views
Skip to first unread message

syzbot

unread,
Oct 29, 2025, 5:50:25 AM (yesterday) Oct 29
to c...@kernel.org, linux-...@vger.kernel.org, linu...@vger.kernel.org, syzkall...@googlegroups.com
Hello xfs maintainers/developers,

This is a 31-day syzbot report for the xfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/xfs

During the period, 1 new issues were detected and 0 were fixed.
In total, 16 issues are still open and 27 have already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 2779 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<2> 254 Yes KASAN: slab-use-after-free Read in xfs_inode_item_push
https://syzkaller.appspot.com/bug?extid=1a28995e12fd13faa44e
<3> 108 Yes INFO: task hung in xfs_buf_item_unpin (2)
https://syzkaller.appspot.com/bug?extid=837bcd54843dd6262f2f
<4> 53 Yes INFO: task hung in vfs_setxattr (7)
https://syzkaller.appspot.com/bug?extid=3d0a18cd22695979a7c6
<5> 17 Yes KASAN: slab-use-after-free Read in xfs_buf_rele (4)
https://syzkaller.appspot.com/bug?extid=0391d34e801643e2809b
<6> 13 Yes KASAN: slab-out-of-bounds Read in xlog_cksum
https://syzkaller.appspot.com/bug?extid=9f6d080dece587cfdd4c
<7> 8 Yes INFO: task hung in xfs_buf_get_map
https://syzkaller.appspot.com/bug?extid=d74d844bdcee0902b28a
<8> 3 Yes INFO: task hung in xlog_force_lsn (2)
https://syzkaller.appspot.com/bug?extid=c27dee924f3271489c82
<9> 1 Yes INFO: task hung in xfs_file_fsync
https://syzkaller.appspot.com/bug?extid=9bc8c0586b39708784d9

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

To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders

To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem

You may send multiple commands in a single email message.

Christoph Hellwig

unread,
3:11 AM (13 hours ago) 3:11 AM
to syzbot+0391d3...@syzkaller.appspotmail.com, linu...@vger.kernel.org, syzkall...@googlegroups.com
#syz test git://git.infradead.org/users/hch/xfs.git xfs-buf-hash

syzbot

unread,
3:42 AM (13 hours ago) 3:42 AM
to h...@infradead.org, linux-...@vger.kernel.org, linu...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to checkout kernel repo git://git.infradead.org/users/hch/xfs.git/xfs-buf-hash: failed to run ["git" "fetch" "--force" "679bdfc056221ae86d16104d6de6223afaafa4b7" "xfs-buf-hash"]: exit status 128


Tested on:

commit: [unknown
git tree: git://git.infradead.org/users/hch/xfs.git xfs-buf-hash
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5ac3d8b8abfcb
dashboard link: https://syzkaller.appspot.com/bug?extid=0391d34e801643e2809b
compiler:
userspace arch: arm64

Note: no patches were applied.

Christoph Hellwig

unread,
4:01 AM (13 hours ago) 4:01 AM
to syzbot+0391d3...@syzkaller.appspotmail.com, linu...@vger.kernel.org, syzkall...@googlegroups.com
#syz test git://git.infradead.org/users/hch/misc.git xfs-buf-hash

syzbot

unread,
4:47 AM (12 hours ago) 4:47 AM
to h...@infradead.org, linux-...@vger.kernel.org, linu...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: MAX_LOCKDEP_CHAINS too low!

BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 1 UID: 0 PID: 2577 Comm: kworker/u8:7 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
Workqueue: xfs-cil/loop0 xlog_cil_push_work
Call trace:
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
__dump_stack+0x30/0x40 lib/dump_stack.c:94
dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
dump_stack+0x1c/0x28 lib/dump_stack.c:129
add_chain_cache kernel/locking/lockdep.c:-1 [inline]
lookup_chain_cache_add kernel/locking/lockdep.c:3855 [inline]
validate_chain kernel/locking/lockdep.c:3876 [inline]
__lock_acquire+0xf9c/0x30a4 kernel/locking/lockdep.c:5237
lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x5c/0x7c kernel/locking/spinlock.c:162
__wake_up_common_lock kernel/sched/wait.c:124 [inline]
__wake_up+0x40/0x1a8 kernel/sched/wait.c:146
xlog_cil_set_ctx_write_state+0x2a8/0x310 fs/xfs/xfs_log_cil.c:997
xlog_write+0x1fc/0xe94 fs/xfs/xfs_log.c:2252
xlog_cil_write_commit_record fs/xfs/xfs_log_cil.c:1118 [inline]
xlog_cil_push_work+0x19ec/0x1f74 fs/xfs/xfs_log_cil.c:1434
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


Tested on:

commit: af1722bb xfs: switch (back) to a per-buftarg buffer hash
git tree: git://git.infradead.org/users/hch/misc.git xfs-buf-hash
console output: https://syzkaller.appspot.com/x/log.txt?x=1110bfe2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=39f8a155475bc42d
dashboard link: https://syzkaller.appspot.com/bug?extid=0391d34e801643e2809b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Reply all
Reply to author
Forward
0 new messages