From: syzbot <syzbot+list7e7905dfe65ae535d3b2@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 (Jan 2025)
Date: Mon, 20 Jan 2025 00:14:24 -0800 [thread overview]
Message-ID: <678e05e0.050a0220.303755.0070.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, 18 issues are still open and 25 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 6194 Yes possible deadlock in xfs_dquot_detach_buf
https://syzkaller.appspot.com/bug?extid=3126ab3db03db42e7a31
<2> 865 Yes KASAN: stack-out-of-bounds Read in xfs_buf_lock
https://syzkaller.appspot.com/bug?extid=0bc698a422b5e4ac988c
<3> 177 Yes KASAN: slab-use-after-free Read in xfs_inode_item_push
https://syzkaller.appspot.com/bug?extid=1a28995e12fd13faa44e
<4> 92 Yes INFO: task hung in xfs_buf_item_unpin (2)
https://syzkaller.appspot.com/bug?extid=837bcd54843dd6262f2f
<5> 10 No possible deadlock in xfs_dquot_disk_alloc
https://syzkaller.appspot.com/bug?extid=0f440b139d96ada5b0fd
<6> 6 No BUG: unable to handle kernel paging request in xfs_destroy_mount_workqueues
https://syzkaller.appspot.com/bug?extid=63340199267472536cf4
---
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-01-20 8:14 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=678e05e0.050a0220.303755.0070.GAE@google.com \
--to=syzbot+list7e7905dfe65ae535d3b2@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