From: syzbot <syzbot+list6d707ca0e4ce5e990ff3@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 (Dec 2023)
Date: Mon, 04 Dec 2023 04:39:24 -0800 [thread overview]
Message-ID: <000000000000724223060bae6880@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, 5 new issues were detected and 0 were fixed.
In total, 88 issues are still open and 17 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 40685 Yes KASAN: null-ptr-deref Read in do_journal_end (2)
https://syzkaller.appspot.com/bug?extid=845cd8e5c47f2a125683
<2> 6321 Yes possible deadlock in open_xa_dir
https://syzkaller.appspot.com/bug?extid=8fb64a61fdd96b50f3b8
<3> 2995 No KASAN: slab-out-of-bounds Read in search_by_key (2)
https://syzkaller.appspot.com/bug?extid=b3b14fb9f8a14c5d0267
<4> 1621 Yes kernel BUG at fs/reiserfs/journal.c:LINE!
https://syzkaller.appspot.com/bug?extid=6820505ae5978f4f8f2f
<5> 1388 Yes possible deadlock in mnt_want_write_file
https://syzkaller.appspot.com/bug?extid=1047e42179f502f2b0a2
<6> 1246 Yes WARNING in reiserfs_lookup
https://syzkaller.appspot.com/bug?extid=392ac209604cc18792e5
<7> 967 No KMSAN: uninit-value in reiserfs_new_inode (2)
https://syzkaller.appspot.com/bug?extid=6450929faa7a97cd42d1
<8> 402 Yes possible deadlock in reiserfs_ioctl
https://syzkaller.appspot.com/bug?extid=79c303ad05f4041e0dad
<9> 380 Yes WARNING in journal_end
https://syzkaller.appspot.com/bug?extid=d43f346675e449548021
<10> 349 Yes possible deadlock in reiserfs_dirty_inode
https://syzkaller.appspot.com/bug?extid=c319bb5b1014113a92cf
---
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-12-04 12:39 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=000000000000724223060bae6880@google.com \
--to=syzbot+list6d707ca0e4ce5e990ff3@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 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).