From: syzbot <syzbot+list020cf39d4baa3eb9d54e@syzkaller.appspotmail.com>
To: djwong@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly xfs report (Jun 2023)
Date: Wed, 07 Jun 2023 02:24:48 -0700 [thread overview]
Message-ID: <0000000000000897b205fd86b576@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, 2 new issues were detected and 0 were fixed.
In total, 22 issues are still open and 21 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1885 No KMSAN: uninit-value in __crc32c_le_base (3)
https://syzkaller.appspot.com/bug?extid=a6d6b8fffa294705dbd8
<2> 188 Yes KASAN: stack-out-of-bounds Read in xfs_buf_lock
https://syzkaller.appspot.com/bug?extid=0bc698a422b5e4ac988c
<3> 127 Yes INFO: task hung in xfs_buf_item_unpin
https://syzkaller.appspot.com/bug?extid=3f083e9e08b726fcfba2
<4> 48 No KCSAN: data-race in __filemap_remove_folio / folio_mapping (2)
https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
<5> 13 No KASAN: use-after-free Read in xfs_inode_item_push
https://syzkaller.appspot.com/bug?extid=f0da51f81ea0b040c803
<6> 7 Yes KASAN: stack-out-of-bounds Read in xfs_buf_delwri_submit_buffers
https://syzkaller.appspot.com/bug?extid=d2cdeba65d32ed1d2c4d
---
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:[~2023-06-07 9:25 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=0000000000000897b205fd86b576@google.com \
--to=syzbot+list020cf39d4baa3eb9d54e@syzkaller.appspotmail.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.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;
as well as URLs for NNTP newsgroup(s).