From: syzbot <syzbot+list9e420ad857ee3276c149@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly nilfs report (Mar 2024)
Date: Tue, 05 Mar 2024 03:10:27 -0800 [thread overview]
Message-ID: <000000000000bf45e60612e7e380@google.com> (raw)
Hello nilfs maintainers/developers,
This is a 31-day syzbot report for the nilfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/nilfs
During the period, 1 new issues were detected and 1 were fixed.
In total, 8 issues are still open and 39 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 518 Yes kernel BUG at fs/buffer.c:LINE!
https://syzkaller.appspot.com/bug?extid=cfed5b56649bddf80d6e
<2> 116 Yes INFO: task hung in nilfs_detach_log_writer
https://syzkaller.appspot.com/bug?extid=e3973c409251e136fdd0
<3> 2 No INFO: task hung in nilfs_segctor_thread (2)
https://syzkaller.appspot.com/bug?extid=c8166c541d3971bf6c87
---
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-03-05 11:10 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=000000000000bf45e60612e7e380@google.com \
--to=syzbot+list9e420ad857ee3276c149@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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.