From: syzbot <syzbot+list7a2521329a03e73f2fa8@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Oct 2023)
Date: Tue, 10 Oct 2023 06:22:54 -0700 [thread overview]
Message-ID: <000000000000b6cc0106075c9a7e@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, 6 new issues were detected and 0 were fixed.
In total, 53 issues are still open and 331 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3341 Yes BUG: sleeping function called from invalid context in __getblk_gfp
https://syzkaller.appspot.com/bug?extid=69b40dc5fd40f32c199f
<2> 2456 Yes WARNING in firmware_fallback_sysfs
https://syzkaller.appspot.com/bug?extid=95f2e2439b97575ec3c0
<3> 1413 Yes possible deadlock in input_event (2)
https://syzkaller.appspot.com/bug?extid=d4c06e848a1c1f9f726f
<4> 327 Yes BUG: sleeping function called from invalid context in __bread_gfp
https://syzkaller.appspot.com/bug?extid=5869fb71f59eac925756
<5> 244 No KASAN: slab-use-after-free Read in __ext4_iget
https://syzkaller.appspot.com/bug?extid=5407ecf3112f882d2ef3
<6> 141 Yes possible deadlock in pipe_write
https://syzkaller.appspot.com/bug?extid=011e4ea1da6692cf881c
<7> 56 Yes WARNING in path_openat
https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
<8> 42 Yes INFO: task hung in filename_create (4)
https://syzkaller.appspot.com/bug?extid=72c5cf124089bc318016
<9> 40 No INFO: task hung in __fdget_pos (4)
https://syzkaller.appspot.com/bug?extid=e245f0516ee625aaa412
<10> 36 Yes INFO: rcu detected stall in sys_clock_adjtime
https://syzkaller.appspot.com/bug?extid=25b7addb06e92c482190
---
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:[~2023-10-10 13:23 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=000000000000b6cc0106075c9a7e@google.com \
--to=syzbot+list7a2521329a03e73f2fa8@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).