From: syzbot <syzbot+list91fd19ac4f0e1b0d9d06-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
Date: Mon, 27 Mar 2023 04:03:43 -0700 [thread overview]
Message-ID: <00000000000037783a05f7dfb2c8@google.com> (raw)
Hello nilfs maintainers/developers,
This is a 30-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, 6 new issues were detected and 1 were fixed.
In total, 20 issues are still open and 16 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
1236 Yes INFO: task hung in lock_mount
https://syzkaller.appspot.com/bug?extid=221d75710bde87fa0e97
901 Yes WARNING in mark_buffer_dirty (4)
https://syzkaller.appspot.com/bug?extid=2af3bc9585be7f23f290
821 No KMSAN: uninit-value in nilfs_add_checksums_on_logs
https://syzkaller.appspot.com/bug?extid=048585f3f4227bb2b49b
404 Yes WARNING in nilfs_btree_assign
https://syzkaller.appspot.com/bug?extid=31837fe952932efc8fb9
316 Yes WARNING in nilfs_sufile_set_segment_usage
https://syzkaller.appspot.com/bug?extid=14e9f834f6ddecece094
169 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
44 Yes INFO: task hung in nilfs_detach_log_writer
https://syzkaller.appspot.com/bug?extid=e3973c409251e136fdd0
13 No KASAN: slab-out-of-bounds Read in nilfs_iget_test
https://syzkaller.appspot.com/bug?extid=cac676135771fc8f1eb2
5 No possible deadlock in nilfs_evict_inode
https://syzkaller.appspot.com/bug?extid=5b7d542076d9bddc3c6a
---
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
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=00000000000037783a05f7dfb2c8@google.com \
--to=syzbot+list91fd19ac4f0e1b0d9d06-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 NNTP newsgroup(s).