From: syzbot <syzbot+list020cb45d6011f314b885@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (May 2023)
Date: Wed, 03 May 2023 00:26:39 -0700 [thread overview]
Message-ID: <0000000000000a842e05fac4fa77@google.com> (raw)
Hello mm maintainers/developers,
This is a 31-day syzbot report for the mm subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/mm
During the period, 7 new issues were detected and 2 were fixed.
In total, 47 issues are still open and 212 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 177 Yes INFO: task hung in do_read_cache_folio
https://syzkaller.appspot.com/bug?extid=be946efe33b2d9664348
<2> 97 Yes INFO: task hung in __filemap_get_folio
https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
<3> 72 Yes KASAN: null-ptr-deref Read in filemap_fault
https://syzkaller.appspot.com/bug?extid=48011b86c8ea329af1b9
<4> 57 Yes WARNING in rcu_check_gp_start_stall
https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa
<5> 15 No possible deadlock in do_writepages
https://syzkaller.appspot.com/bug?extid=6898da502aef574c5f8a
<6> 5 No kernel BUG in truncate_inode_partial_folio
https://syzkaller.appspot.com/bug?extid=77184b5e843d90d56ec1
---
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-05-03 7:26 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=0000000000000a842e05fac4fa77@google.com \
--to=syzbot+list020cb45d6011f314b885@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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