From: syzbot <syzbot+list44baf210a6a389320a95@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Jul 2024)
Date: Thu, 18 Jul 2024 00:59:23 -0700 [thread overview]
Message-ID: <000000000000f5cb0b061d80f4e1@google.com> (raw)
Hello fs maintainers/developers,
This is a 31-day syzbot report for the fs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/fs
During the period, 4 new issues were detected and 0 were fixed.
In total, 40 issues are still open and 349 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4025 Yes possible deadlock in input_event (2)
https://syzkaller.appspot.com/bug?extid=d4c06e848a1c1f9f726f
<2> 2605 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<3> 1138 Yes WARNING in inc_nlink (3)
https://syzkaller.appspot.com/bug?extid=2b3af42c0644df1e4da9
<4> 1094 Yes INFO: task hung in filename_create (4)
https://syzkaller.appspot.com/bug?extid=72c5cf124089bc318016
<5> 825 Yes INFO: task hung in d_alloc_parallel (2)
https://syzkaller.appspot.com/bug?extid=55f124a35eac76b52fb7
<6> 575 Yes general protection fault in iter_file_splice_write
https://syzkaller.appspot.com/bug?extid=d2125fcb6aa8c4276fd2
<7> 445 Yes INFO: task hung in synchronize_rcu (4)
https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
<8> 349 Yes INFO: task hung in user_get_super (2)
https://syzkaller.appspot.com/bug?extid=ba09f4a317431df6cddf
<9> 320 Yes WARNING: proc registration bug in bcm_connect
https://syzkaller.appspot.com/bug?extid=df49d48077305d17519a
<10> 295 Yes KASAN: use-after-free Read in sysv_new_inode (2)
https://syzkaller.appspot.com/bug?extid=8d075c0e52baab2345e2
---
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-07-18 7:59 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=000000000000f5cb0b061d80f4e1@google.com \
--to=syzbot+list44baf210a6a389320a95@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).