From: syzbot <syzbot+list7ecb28f76477d00e16c9@syzkaller.appspotmail.com>
To: chandan.babu@oracle.com, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly xfs report (May 2024)
Date: Thu, 30 May 2024 23:48:32 -0700 [thread overview]
Message-ID: <00000000000032c4940619ba5fa1@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, 7 new issues were detected and 0 were fixed.
In total, 14 issues are still open and 22 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 790 No possible deadlock in xfs_ilock (2)
https://syzkaller.appspot.com/bug?extid=c6d7bff58a2218f14632
<2> 696 Yes KASAN: stack-out-of-bounds Read in xfs_buf_lock
https://syzkaller.appspot.com/bug?extid=0bc698a422b5e4ac988c
<3> 59 No possible deadlock in xfs_icwalk_ag (2)
https://syzkaller.appspot.com/bug?extid=4248e91deb3db78358a2
<4> 25 No KASAN: slab-use-after-free Read in xfs_inode_item_push
https://syzkaller.appspot.com/bug?extid=1a28995e12fd13faa44e
<5> 24 No general protection fault in xfs_destroy_mount_workqueues
https://syzkaller.appspot.com/bug?extid=8905ded1b49ae88b96a6
<6> 1 No WARNING in mod_delayed_work_on
https://syzkaller.appspot.com/bug?extid=d9c37490b32d66c6bc78
<7> 1 No possible deadlock in xfs_ilock_attr_map_shared
https://syzkaller.appspot.com/bug?extid=069cc167ecbee6e3e91a
---
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:[~2024-05-31 6:48 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=00000000000032c4940619ba5fa1@google.com \
--to=syzbot+list7ecb28f76477d00e16c9@syzkaller.appspotmail.com \
--cc=chandan.babu@oracle.com \
--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