From: syzbot <syzbot+list6b89f8f9cf475b7afecf@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (May 2026)
Date: Sat, 23 May 2026 05:32:43 -0700 [thread overview]
Message-ID: <6a119e6b.170a0220.35b2b7.000b.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, 10 new issues were detected and 0 were fixed.
In total, 108 issues are still open and 370 have already been fixed.
There are also 14 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3645 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<2> 1005 No KCSAN: data-race in __filemap_remove_folio / folio_mapping (2)
https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
<3> 144 Yes INFO: rcu detected stall in sys_unshare (9)
https://syzkaller.appspot.com/bug?extid=872bccd9a68c6ba47718
<4> 74 Yes INFO: rcu detected stall in sys_setsockopt (4)
https://syzkaller.appspot.com/bug?extid=6e61d59e9d2150c8492b
<5> 45 Yes memory leak in xas_create
https://syzkaller.appspot.com/bug?extid=a785d07959bc94837d51
<6> 8 Yes INFO: rcu detected stall in kernfs_fop_open (7)
https://syzkaller.appspot.com/bug?extid=19d01f6082ec61dd45b2
<7> 6 Yes INFO: rcu detected stall in sys_symlink (6)
https://syzkaller.appspot.com/bug?extid=e538d3da32f1c0337b01
<8> 10396 Yes KASAN: use-after-free Read in copy_folio_from_iter_atomic (2)
https://syzkaller.appspot.com/bug?extid=6cc93ec9a4035badb85f
<9> 7470 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<10> 1667 No possible deadlock in lock_mm_and_find_vma (4)
https://syzkaller.appspot.com/bug?extid=709f5ab0e03871dec50a
---
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-05-23 12: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=6a119e6b.170a0220.35b2b7.000b.GAE@google.com \
--to=syzbot+list6b89f8f9cf475b7afecf@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