From: syzbot <syzbot+list5548945be6cdbe1097d9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Jun 2026)
Date: Tue, 23 Jun 2026 13:32:28 -0700 [thread overview]
Message-ID: <6a3aed5c.b0c80a11.da7f.0004.GAE@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 0 were fixed.
In total, 86 issues are still open and 373 have already been fixed.
There are also 44 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 20360 Yes KASAN: use-after-free Read in copy_folio_from_iter_atomic (2)
https://syzkaller.appspot.com/bug?extid=6cc93ec9a4035badb85f
<2> 10103 Yes WARNING in hrtick_start_fair
https://syzkaller.appspot.com/bug?extid=2cbf10efc23b22ff9c31
<3> 3807 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<4> 495 Yes kernel BUG in filemap_unaccount_folio
https://syzkaller.appspot.com/bug?extid=17a207d226b8a5fb0fd9
<5> 194 No INFO: task hung in migrate_pages_batch (4)
https://syzkaller.appspot.com/bug?extid=f523acb98cd782b4872e
<6> 132 Yes INFO: rcu detected stall in __dentry_kill
https://syzkaller.appspot.com/bug?extid=f8ccdac0a7eede0e1ae5
<7> 87 Yes INFO: rcu detected stall in sys_setsockopt (4)
https://syzkaller.appspot.com/bug?extid=6e61d59e9d2150c8492b
<8> 76 Yes KASAN: slab-use-after-free Read in folio_evictable (3)
https://syzkaller.appspot.com/bug?extid=4c7590f1cee06597e43a
<9> 50 Yes memory leak in xas_create
https://syzkaller.appspot.com/bug?extid=a785d07959bc94837d51
<10> 19 Yes INFO: task hung in writeback_iter (3)
https://syzkaller.appspot.com/bug?extid=1e3ff4b07c16ca0f6fe2
---
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:[~2026-06-23 20:32 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=6a3aed5c.b0c80a11.da7f.0004.GAE@google.com \
--to=syzbot+list5548945be6cdbe1097d9@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 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.