From: syzbot <syzbot+listf1f846890378c60ccd2e@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 (Aug 2025)
Date: Wed, 27 Aug 2025 01:15:34 -0700 [thread overview]
Message-ID: <68aebea6.a70a0220.3cafd4.0015.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, 4 new issues were detected and 0 were fixed.
In total, 14 issues are still open and 27 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2624 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<2> 271 Yes BUG: Bad page state in iomap_write_begin
https://syzkaller.appspot.com/bug?extid=c317c107c68f8bc257d9
<3> 215 Yes KASAN: slab-use-after-free Read in xfs_inode_item_push
https://syzkaller.appspot.com/bug?extid=1a28995e12fd13faa44e
<4> 29 Yes INFO: task hung in vfs_setxattr (7)
https://syzkaller.appspot.com/bug?extid=3d0a18cd22695979a7c6
<5> 2 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:[~2025-08-27 8:15 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=68aebea6.a70a0220.3cafd4.0015.GAE@google.com \
--to=syzbot+listf1f846890378c60ccd2e@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 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.