From: syzbot <syzbot+list879a30818ab26ff997d4-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
To: konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: [syzbot] Monthly nilfs report (Jul 2023)
Date: Sun, 30 Jul 2023 06:15:04 -0700 [thread overview]
Message-ID: <0000000000002087490601b41a01@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 0 were fixed.
In total, 12 issues are still open and 33 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 274 Yes kernel BUG at fs/buffer.c:LINE!
https://syzkaller.appspot.com/bug?extid=cfed5b56649bddf80d6e
<2> 110 Yes WARNING in mark_buffer_dirty (5)
https://syzkaller.appspot.com/bug?extid=cdfcae656bac88ba0e2d
<3> 80 Yes INFO: task hung in nilfs_detach_log_writer
https://syzkaller.appspot.com/bug?extid=e3973c409251e136fdd0
<4> 5 Yes general protection fault in folio_create_empty_buffers
https://syzkaller.appspot.com/bug?extid=0ad741797f4565e7e2d2
<5> 5 Yes kernel BUG in end_buffer_async_write
https://syzkaller.appspot.com/bug?extid=5c04210f7c7f897c1e7f
---
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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
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-07-30 13:15 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=0000000000002087490601b41a01@google.com \
--to=syzbot+list879a30818ab26ff997d4-pl5pbv+gp7p466ipttivnc23woclnbcfal8byrjmmd8@public.gmane.org \
--cc=konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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).