From: syzbot <syzbot+listead278fb97880f3601f8@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly btrfs report (May 2024)
Date: Mon, 13 May 2024 14:13:22 -0700 [thread overview]
Message-ID: <000000000000fa454606185c5a0d@google.com> (raw)
Hello btrfs maintainers/developers,
This is a 31-day syzbot report for the btrfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/btrfs
During the period, 2 new issues were detected and 1 were fixed.
In total, 39 issues are still open and 54 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 5930 Yes kernel BUG in close_ctree
https://syzkaller.appspot.com/bug?extid=2665d678fffcc4608e18
<2> 2988 Yes WARNING in btrfs_space_info_update_bytes_may_use
https://syzkaller.appspot.com/bug?extid=8edfa01e46fd9fe3fbfb
<3> 322 Yes kernel BUG at fs/inode.c:LINE! (2)
https://syzkaller.appspot.com/bug?extid=c92c93d1f1aaaacdb9db
<4> 286 Yes WARNING in __btrfs_free_extent
https://syzkaller.appspot.com/bug?extid=560e6a32d484d7293e37
<5> 227 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
<6> 123 Yes WARNING in btrfs_commit_transaction (2)
https://syzkaller.appspot.com/bug?extid=dafbca0e20fbc5946925
<7> 114 Yes kernel BUG in btrfs_free_tree_block
https://syzkaller.appspot.com/bug?extid=a306f914b4d01b3958fe
<8> 97 Yes WARNING in cleanup_transaction
https://syzkaller.appspot.com/bug?extid=021d10c4d4edc87daa03
<9> 97 Yes kernel BUG in set_state_bits
https://syzkaller.appspot.com/bug?extid=b9d2e54d2301324657ed
<10> 83 Yes WARNING in btrfs_put_transaction
https://syzkaller.appspot.com/bug?extid=3706b1df47f2464f0c1e
---
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-13 21:13 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=000000000000fa454606185c5a0d@google.com \
--to=syzbot+listead278fb97880f3601f8@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 read-only IMAP folder(s) and NNTP newsgroup(s).