From: syzbot <syzbot+list3e0431ddab075345f512@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 (May 2023)
Date: Tue, 30 May 2023 01:21:55 -0700 [thread overview]
Message-ID: <000000000000716a8005fce4e592@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, 5 new issues were detected and 1 were fixed.
In total, 52 issues are still open and 26 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2986 Yes kernel BUG in close_ctree
https://syzkaller.appspot.com/bug?extid=2665d678fffcc4608e18
<2> 677 Yes VFS: Busy inodes after unmount (use-after-free)
https://syzkaller.appspot.com/bug?extid=0af00f6a2cba2058b5db
<3> 424 Yes WARNING in __kernel_write_iter
https://syzkaller.appspot.com/bug?extid=12e098239d20385264d3
<4> 381 Yes WARNING in btrfs_space_info_update_bytes_may_use
https://syzkaller.appspot.com/bug?extid=8edfa01e46fd9fe3fbfb
<5> 370 Yes WARNING in btrfs_block_rsv_release
https://syzkaller.appspot.com/bug?extid=dde7e853812ed57835ea
<6> 193 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
<7> 191 Yes WARNING in lookup_inline_extent_backref
https://syzkaller.appspot.com/bug?extid=d6f9ff86c1d804ba2bc6
<8> 189 Yes WARNING in btrfs_chunk_alloc
https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
<9> 184 Yes possible deadlock in btrfs_search_slot
https://syzkaller.appspot.com/bug?extid=c06034aecf9f5eab1ac1
<10> 151 Yes kernel BUG in assertfail (2)
https://syzkaller.appspot.com/bug?extid=c4614eae20a166c25bf0
---
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-05-30 8:22 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=000000000000716a8005fce4e592@google.com \
--to=syzbot+list3e0431ddab075345f512@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.