From: syzbot <syzbot+listc1ea4dfa31fea8381e9d@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Mar 2024)
Date: Sat, 16 Mar 2024 05:09:25 -0700 [thread overview]
Message-ID: <000000000000de9d170613c5fe46@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, 1 new issues were detected and 1 were fixed.
In total, 40 issues are still open and 341 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 233 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<2> 210 Yes INFO: task hung in user_get_super (2)
https://syzkaller.appspot.com/bug?extid=ba09f4a317431df6cddf
<3> 73 Yes INFO: task hung in __fdget_pos (4)
https://syzkaller.appspot.com/bug?extid=e245f0516ee625aaa412
<4> 62 Yes INFO: task hung in filename_create (4)
https://syzkaller.appspot.com/bug?extid=72c5cf124089bc318016
<5> 45 Yes INFO: rcu detected stall in sys_clock_adjtime
https://syzkaller.appspot.com/bug?extid=25b7addb06e92c482190
<6> 36 Yes INFO: task hung in synchronize_rcu (4)
https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
<7> 35 Yes WARNING: proc registration bug in bcm_connect
https://syzkaller.appspot.com/bug?extid=df49d48077305d17519a
<8> 21 Yes BUG: unable to handle kernel NULL pointer dereference in do_pagemap_scan
https://syzkaller.appspot.com/bug?extid=f9238a0a31f9b5603fef
<9> 13 Yes KASAN: use-after-free Read in sysv_new_block
https://syzkaller.appspot.com/bug?extid=eda782c229b243c648e9
<10> 3 Yes WARNING in pagemap_scan_pmd_entry (2)
https://syzkaller.appspot.com/bug?extid=0748a3a1931714d970d0
---
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-16 12:09 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=000000000000de9d170613c5fe46@google.com \
--to=syzbot+listc1ea4dfa31fea8381e9d@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