From: syzbot <syzbot+listb85a7a162ab0a876fae7@syzkaller.appspotmail.com>
To: cem@kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly xfs report (Jan 2026)
Date: Fri, 30 Jan 2026 02:09:27 -0800 [thread overview]
Message-ID: <697c8357.a70a0220.9914.0484.GAE@google.com> (raw)
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, 3 new issues were detected and 0 were fixed.
In total, 21 issues are still open and 27 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3445 Yes possible deadlock in xfs_buffered_write_iomap_begin
https://syzkaller.appspot.com/bug?extid=5f5f36a9ed0aadd614f3
<2> 853 Yes possible deadlock in xfs_icwalk_ag (3)
https://syzkaller.appspot.com/bug?extid=789028412a4af61a2b61
<3> 318 Yes KASAN: slab-use-after-free Read in xfs_inode_item_push
https://syzkaller.appspot.com/bug?extid=1a28995e12fd13faa44e
<4> 113 Yes INFO: task hung in xfs_buf_item_unpin (2)
https://syzkaller.appspot.com/bug?extid=837bcd54843dd6262f2f
<5> 107 No possible deadlock in xfs_can_free_eofblocks (3)
https://syzkaller.appspot.com/bug?extid=a8a73f25200041b89d40
<6> 20 No possible deadlock in xfs_trans_alloc
https://syzkaller.appspot.com/bug?extid=f4c587833618ec4a76f9
<7> 9 No general protection fault in workingset_refault (3)
https://syzkaller.appspot.com/bug?extid=ccf9f05f06b4b951f3cd
<8> 8 Yes KASAN: slab-use-after-free Write in xlog_cil_committed
https://syzkaller.appspot.com/bug?extid=4e6ee73c0ae4b6e8753f
<9> 4 Yes KASAN: slab-use-after-free Read in xlog_cil_push_work
https://syzkaller.appspot.com/bug?extid=95170b2e7d9e80b8a7d7
---
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.
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.
reply other threads:[~2026-01-30 10:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=697c8357.a70a0220.9914.0484.GAE@google.com \
--to=syzbot+listb85a7a162ab0a876fae7@syzkaller.appspotmail.com \
--cc=cem@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox