From: syzbot <syzbot+listad2f01a497df9ab5d719@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly btrfs report (Feb 2024)
Date: Fri, 09 Feb 2024 12:57:24 -0800 [thread overview]
Message-ID: <000000000000c47db50610f92cf9@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, 1 new issues were detected and 1 were fixed.
In total, 43 issues are still open and 51 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 5804 Yes kernel BUG in close_ctree
https://syzkaller.appspot.com/bug?extid=2665d678fffcc4608e18
<2> 2636 Yes WARNING in btrfs_space_info_update_bytes_may_use
https://syzkaller.appspot.com/bug?extid=8edfa01e46fd9fe3fbfb
<3> 251 Yes INFO: task hung in lock_extent
https://syzkaller.appspot.com/bug?extid=eaa05fbc7563874b7ad2
<4> 245 Yes WARNING in btrfs_chunk_alloc
https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
<5> 224 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
<6> 125 Yes kernel BUG in insert_state_fast
https://syzkaller.appspot.com/bug?extid=9ce4a36127ca92b59677
<7> 99 Yes kernel BUG in btrfs_free_tree_block
https://syzkaller.appspot.com/bug?extid=a306f914b4d01b3958fe
<8> 88 Yes kernel BUG in set_state_bits
https://syzkaller.appspot.com/bug?extid=b9d2e54d2301324657ed
<9> 79 Yes WARNING in btrfs_commit_transaction (2)
https://syzkaller.appspot.com/bug?extid=dafbca0e20fbc5946925
<10> 74 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.
next reply other threads:[~2024-02-09 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 20:57 syzbot [this message]
2024-02-10 8:48 ` [syzbot] Monthly btrfs report (Feb 2024) Qu Wenruo
2024-02-12 12:15 ` Aleksandr Nogikh
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=000000000000c47db50610f92cf9@google.com \
--to=syzbot+listad2f01a497df9ab5d719@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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 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.