From: syzbot <syzbot+listf919ad9f1f609cd7cf5d-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 (Apr 2023)
Date: Thu, 27 Apr 2023 03:39:38 -0700 [thread overview]
Message-ID: <00000000000032c8c505fa4ef9cc@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 3 were fixed.
In total, 17 issues are still open and 24 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1238 Yes INFO: task hung in lock_mount
https://syzkaller.appspot.com/bug?extid=221d75710bde87fa0e97
<2> 605 Yes WARNING in nilfs_btree_assign
https://syzkaller.appspot.com/bug?extid=31837fe952932efc8fb9
<3> 321 Yes WARNING in nilfs_sufile_set_segment_usage
https://syzkaller.appspot.com/bug?extid=14e9f834f6ddecece094
<4> 241 Yes INFO: task hung in sync_inodes_sb (4)
https://syzkaller.appspot.com/bug?extid=7d50f1e54a12ba3aeae2
<5> 195 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<6> 55 Yes INFO: task hung in nilfs_detach_log_writer
https://syzkaller.appspot.com/bug?extid=e3973c409251e136fdd0
<7> 28 Yes kernel BUG in folio_end_writeback
https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
<8> 21 No KASAN: slab-out-of-bounds Read in nilfs_iget_test
https://syzkaller.appspot.com/bug?extid=cac676135771fc8f1eb2
<9> 6 No BUG: unable to handle kernel NULL pointer dereference in nilfs_segctor_do_construct
https://syzkaller.appspot.com/bug?extid=5afc832d6dbb2fd17538
<10> 3 No WARNING in nilfs_btree_propagate
https://syzkaller.appspot.com/bug?extid=527641d191abe35993c1
---
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.
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+listf919ad9f1f609cd7cf5d@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 (Apr 2023)
Date: Thu, 27 Apr 2023 03:39:38 -0700 [thread overview]
Message-ID: <00000000000032c8c505fa4ef9cc@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 3 were fixed.
In total, 17 issues are still open and 24 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1238 Yes INFO: task hung in lock_mount
https://syzkaller.appspot.com/bug?extid=221d75710bde87fa0e97
<2> 605 Yes WARNING in nilfs_btree_assign
https://syzkaller.appspot.com/bug?extid=31837fe952932efc8fb9
<3> 321 Yes WARNING in nilfs_sufile_set_segment_usage
https://syzkaller.appspot.com/bug?extid=14e9f834f6ddecece094
<4> 241 Yes INFO: task hung in sync_inodes_sb (4)
https://syzkaller.appspot.com/bug?extid=7d50f1e54a12ba3aeae2
<5> 195 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<6> 55 Yes INFO: task hung in nilfs_detach_log_writer
https://syzkaller.appspot.com/bug?extid=e3973c409251e136fdd0
<7> 28 Yes kernel BUG in folio_end_writeback
https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
<8> 21 No KASAN: slab-out-of-bounds Read in nilfs_iget_test
https://syzkaller.appspot.com/bug?extid=cac676135771fc8f1eb2
<9> 6 No BUG: unable to handle kernel NULL pointer dereference in nilfs_segctor_do_construct
https://syzkaller.appspot.com/bug?extid=5afc832d6dbb2fd17538
<10> 3 No WARNING in nilfs_btree_propagate
https://syzkaller.appspot.com/bug?extid=527641d191abe35993c1
---
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.
next reply other threads:[~2023-04-27 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 10:39 syzbot [this message]
2023-04-27 10:39 ` [syzbot] Monthly nilfs report (Apr 2023) syzbot
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=00000000000032c8c505fa4ef9cc@google.com \
--to=syzbot+listf919ad9f1f609cd7cf5d-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 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.