From: syzbot <syzbot+list9522b235663d5a4f6672@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Sep 2026)
Date: Fri, 25 Sep 2026 05:33:38 -0700 [thread overview]
Message-ID: <6ab66a22.80e1c6cc.1e8e5f.0031.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, 2 new issues were detected and 1 were fixed.
In total, 76 issues are still open and 382 have already been fixed.
There are also 39 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3955 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<2> 3805 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
<3> 3136 Yes possible deadlock in filemap_fault
https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<4> 638 Yes INFO: rcu detected stall in sys_newfstatat (4)
https://syzkaller.appspot.com/bug?extid=1c02a56102605204445c
<5> 528 Yes kernel BUG in filemap_unaccount_folio
https://syzkaller.appspot.com/bug?extid=17a207d226b8a5fb0fd9
<6> 329 No kernel BUG in __page_table_check_zero (3)
https://syzkaller.appspot.com/bug?extid=2b5fe617654be3d8848b
<7> 308 No INFO: task hung in migrate_pages_batch (4)
https://syzkaller.appspot.com/bug?extid=f523acb98cd782b4872e
<8> 185 Yes INFO: rcu detected stall in sys_unshare (9)
https://syzkaller.appspot.com/bug?extid=872bccd9a68c6ba47718
<9> 166 Yes WARNING in ext4_mb_load_buddy_gfp
https://syzkaller.appspot.com/bug?extid=fd3f70a4509fca8c265d
<10> 115 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-09-25 12: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=6ab66a22.80e1c6cc.1e8e5f.0031.GAE@google.com \
--to=syzbot+list9522b235663d5a4f6672@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
all inboxes | Powered by JetHome®