From: syzbot <syzbot+list63b3a3942997eecbf429@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 (Feb 2024)
Date: Sun, 04 Feb 2024 05:30:25 -0800 [thread overview]
Message-ID: <000000000000107f6106108e5995@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 0 were fixed.
In total, 68 issues are still open and 28 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7667 Yes possible deadlock in open_xa_dir
https://syzkaller.appspot.com/bug?extid=8fb64a61fdd96b50f3b8
<2> 1675 Yes possible deadlock in mnt_want_write_file
https://syzkaller.appspot.com/bug?extid=1047e42179f502f2b0a2
<3> 1339 Yes KMSAN: uninit-value in reiserfs_new_inode (2)
https://syzkaller.appspot.com/bug?extid=6450929faa7a97cd42d1
<4> 522 Yes WARNING in journal_end
https://syzkaller.appspot.com/bug?extid=d43f346675e449548021
<5> 519 Yes possible deadlock in reiserfs_dirty_inode
https://syzkaller.appspot.com/bug?extid=c319bb5b1014113a92cf
<6> 327 Yes KASAN: out-of-bounds Read in leaf_paste_entries (2)
https://syzkaller.appspot.com/bug?extid=38b79774b6c990637f95
<7> 310 Yes KASAN: use-after-free Read in leaf_paste_in_buffer
https://syzkaller.appspot.com/bug?extid=55b82aea13452e3d128f
<8> 305 Yes possible deadlock in path_openat (2)
https://syzkaller.appspot.com/bug?extid=a844a888fbc0ba4829ce
<9> 278 No KASAN: slab-use-after-free Read in __ext4_iget
https://syzkaller.appspot.com/bug?extid=5407ecf3112f882d2ef3
<10> 225 Yes possible deadlock in vm_mmap_pgoff
https://syzkaller.appspot.com/bug?extid=f619f7c0a2a5f87694e6
---
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:[~2024-02-04 13:30 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=000000000000107f6106108e5995@google.com \
--to=syzbot+list63b3a3942997eecbf429@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).