From: syzbot <syzbot+list4a0f973260c9d6cd4fb2@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
Date: Mon, 27 Mar 2023 04:03:43 -0700 [thread overview]
Message-ID: <0000000000003bdd5d05f7dfb243@google.com> (raw)
Hello reiserfs maintainers/developers,
This is a 30-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, 4 new issues were detected and 0 were fixed.
In total, 78 issues are still open and 16 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
1220 No KASAN: slab-out-of-bounds Read in search_by_key (2)
https://syzkaller.appspot.com/bug?extid=b3b14fb9f8a14c5d0267
1096 Yes WARNING in reiserfs_lookup
https://syzkaller.appspot.com/bug?extid=392ac209604cc18792e5
1069 Yes kernel BUG at fs/reiserfs/journal.c:LINE!
https://syzkaller.appspot.com/bug?extid=6820505ae5978f4f8f2f
853 Yes INFO: task hung in iterate_supers
https://syzkaller.appspot.com/bug?extid=2349f5067b1772c1d8a5
565 No KMSAN: uninit-value in reiserfs_new_inode (2)
https://syzkaller.appspot.com/bug?extid=6450929faa7a97cd42d1
331 Yes possible deadlock in mnt_want_write_file
https://syzkaller.appspot.com/bug?extid=1047e42179f502f2b0a2
168 Yes possible deadlock in reiserfs_ioctl
https://syzkaller.appspot.com/bug?extid=79c303ad05f4041e0dad
122 Yes WARNING in reiserfs_readdir_inode
https://syzkaller.appspot.com/bug?extid=798ffe5fe3e88235db59
54 Yes possible deadlock in path_openat (2)
https://syzkaller.appspot.com/bug?extid=a844a888fbc0ba4829ce
45 Yes BUG: unable to handle kernel paging request in path_openat
https://syzkaller.appspot.com/bug?extid=59a66cac604a6b49ecce
---
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.
reply other threads:[~2023-03-27 11:03 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=0000000000003bdd5d05f7dfb243@google.com \
--to=syzbot+list4a0f973260c9d6cd4fb2@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.