From: syzbot <syzbot+listea0b12829deaef4101fd@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
Date: Thu, 30 Mar 2023 02:58:43 -0700 [thread overview]
Message-ID: <000000000000529f1805f81b23c2@google.com> (raw)
Hello xfs maintainers/developers,
This is a 30-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, 5 new issues were detected and 0 were fixed.
In total, 23 issues are still open and 15 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
327 Yes INFO: task hung in xlog_grant_head_check
https://syzkaller.appspot.com/bug?extid=568245b88fbaedcb1959
85 Yes KASAN: stack-out-of-bounds Read in xfs_buf_lock
https://syzkaller.appspot.com/bug?extid=0bc698a422b5e4ac988c
81 Yes WARNING in xfs_qm_dqget_cache_insert
https://syzkaller.appspot.com/bug?extid=6ae213503fb12e87934f
47 Yes WARNING in xfs_bmapi_convert_delalloc
https://syzkaller.appspot.com/bug?extid=53b443b5c64221ee8bad
44 Yes INFO: task hung in xfs_buf_item_unpin
https://syzkaller.appspot.com/bug?extid=3f083e9e08b726fcfba2
13 Yes general protection fault in __xfs_free_extent
https://syzkaller.appspot.com/bug?extid=bfbc1eecdfb9b10e5792
5 Yes KASAN: use-after-free Read in xfs_btree_lookup_get_block
https://syzkaller.appspot.com/bug?extid=7e9494b8b399902e994e
---
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.
next reply other threads:[~2023-03-30 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:58 syzbot [this message]
2023-04-11 1:35 ` [syzbot] Monthly xfs report Dave Chinner
2023-04-11 4:35 ` Darrick J. Wong
2023-04-12 21:54 ` Dave Chinner
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=000000000000529f1805f81b23c2@google.com \
--to=syzbot+listea0b12829deaef4101fd@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).