From: syzbot <syzbot+list614ad8fd5d6c3f525723@syzkaller.appspotmail.com>
To: chandan.babu@oracle.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly xfs report (Nov 2023)
Date: Wed, 08 Nov 2023 15:44:22 -0800 [thread overview]
Message-ID: <000000000000a3bd1e0609acaa04@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, 0 new issues were detected and 0 were fixed.
In total, 13 issues are still open and 18 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8235 No KMSAN: uninit-value in __crc32c_le_base (3)
https://syzkaller.appspot.com/bug?extid=a6d6b8fffa294705dbd8
<2> 291 Yes KASAN: stack-out-of-bounds Read in xfs_buf_lock
https://syzkaller.appspot.com/bug?extid=0bc698a422b5e4ac988c
<3> 147 Yes INFO: task hung in xfs_buf_item_unpin
https://syzkaller.appspot.com/bug?extid=3f083e9e08b726fcfba2
<4> 134 Yes WARNING in print_bfs_bug (2)
https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
<5> 101 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<6> 4 Yes WARNING: Reset corrupted AGFL on AG NUM. NUM blocks leaked. Please unmount and run xfs_repair.
https://syzkaller.appspot.com/bug?extid=9d0b0d54a8bd799f6ae4
---
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-11-08 23:44 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=000000000000a3bd1e0609acaa04@google.com \
--to=syzbot+list614ad8fd5d6c3f525723@syzkaller.appspotmail.com \
--cc=chandan.babu@oracle.com \
--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 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.