From: syzbot <syzbot+list72238feb199a0257ca76@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Oct 2026)
Date: Mon, 26 Oct 2026 13:33:43 -0700 [thread overview]
Message-ID: <6adfb927.3a3d6196.2ecadf.0021.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, 4 new issues were detected and 0 were fixed.
In total, 79 issues are still open and 386 have already been fixed.
There are also 37 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 45812 Yes KASAN: use-after-free Read in copy_folio_from_iter_atomic (2)
https://syzkaller.appspot.com/bug?extid=6cc93ec9a4035badb85f
<2> 4126 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<3> 648 Yes INFO: rcu detected stall in sys_newfstatat (4)
https://syzkaller.appspot.com/bug?extid=1c02a56102605204445c
<4> 536 Yes kernel BUG in filemap_unaccount_folio
https://syzkaller.appspot.com/bug?extid=17a207d226b8a5fb0fd9
<5> 444 Yes WARNING in ext4_mb_load_buddy_gfp
https://syzkaller.appspot.com/bug?extid=fd3f70a4509fca8c265d
<6> 361 No kernel BUG in __page_table_check_zero (3)
https://syzkaller.appspot.com/bug?extid=2b5fe617654be3d8848b
<7> 324 Yes kernel panic: System is deadlocked on memory (2)
https://syzkaller.appspot.com/bug?extid=c61d6962d0b7e698439e
<8> 189 Yes INFO: rcu detected stall in sys_unshare (9)
https://syzkaller.appspot.com/bug?extid=872bccd9a68c6ba47718
<9> 126 Yes INFO: rcu detected stall in dentry_kill
https://syzkaller.appspot.com/bug?extid=0635dc2e2c3c21a6aa04
<10> 124 Yes INFO: rcu detected stall in sys_setsockopt (4)
https://syzkaller.appspot.com/bug?extid=6e61d59e9d2150c8492b
---
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-10-26 20:33 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=6adfb927.3a3d6196.2ecadf.0021.GAE@google.com \
--to=syzbot+list72238feb199a0257ca76@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.