From: syzbot <syzbot+listc7e3fffb336c714441aa@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly reiserfs report (May 2023)
Date: Mon, 29 May 2023 01:47:55 -0700 [thread overview]
Message-ID: <00000000000098177b05fcd124f6@google.com> (raw)
Hello reiserfs maintainers/developers,
This is a 31-day syzbot report for the reiserfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/reiserfs
During the period, 2 new issues were detected and 1 were fixed.
In total, 71 issues are still open and 16 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1958 Yes possible deadlock in open_xa_dir
https://syzkaller.appspot.com/bug?extid=8fb64a61fdd96b50f3b8
<2> 1597 No KASAN: slab-out-of-bounds Read in search_by_key (2)
https://syzkaller.appspot.com/bug?extid=b3b14fb9f8a14c5d0267
<3> 1455 Yes kernel BUG in do_journal_begin_r
https://syzkaller.appspot.com/bug?extid=2da5e132dd0268a9c0e4
<4> 1315 Yes kernel BUG at fs/reiserfs/journal.c:LINE!
https://syzkaller.appspot.com/bug?extid=6820505ae5978f4f8f2f
<5> 1184 Yes WARNING in reiserfs_lookup
https://syzkaller.appspot.com/bug?extid=392ac209604cc18792e5
<6> 597 Yes possible deadlock in mnt_want_write_file
https://syzkaller.appspot.com/bug?extid=1047e42179f502f2b0a2
<7> 242 Yes possible deadlock in reiserfs_ioctl
https://syzkaller.appspot.com/bug?extid=79c303ad05f4041e0dad
<8> 218 Yes possible deadlock in do_journal_begin_r
https://syzkaller.appspot.com/bug?extid=5e385bfa7d505b075d9f
<9> 187 Yes KASAN: out-of-bounds Read in leaf_paste_entries (2)
https://syzkaller.appspot.com/bug?extid=38b79774b6c990637f95
<10> 159 Yes WARNING in journal_end
https://syzkaller.appspot.com/bug?extid=d43f346675e449548021
---
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-29 8:47 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=00000000000098177b05fcd124f6@google.com \
--to=syzbot+listc7e3fffb336c714441aa@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@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.