From: syzbot <syzbot+listaebfd2e176cddedda623@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Apr 2026)
Date: Wed, 22 Apr 2026 02:08:35 -0700 [thread overview]
Message-ID: <69e89013.a00a0220.17a17.0029.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 1 were fixed.
In total, 130 issues are still open and 369 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 24253 Yes WARNING in path_noexec (2)
https://syzkaller.appspot.com/bug?extid=a9391462075ffb9f77c6
<2> 7462 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<3> 1919 Yes kernel BUG in __filemap_add_folio
https://syzkaller.appspot.com/bug?extid=4d3cc33ef7a77041efa6
<4> 1762 Yes KASAN: use-after-free Read in copy_folio_from_iter_atomic (2)
https://syzkaller.appspot.com/bug?extid=6cc93ec9a4035badb85f
<5> 976 No KCSAN: data-race in __filemap_remove_folio / folio_mapping (2)
https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
<6> 927 No possible deadlock in lock_mm_and_find_vma (4)
https://syzkaller.appspot.com/bug?extid=709f5ab0e03871dec50a
<7> 701 Yes INFO: rcu detected stall in addrconf_rs_timer (6)
https://syzkaller.appspot.com/bug?extid=fecf8bd19c1f78edb255
<8> 689 Yes INFO: task hung in _vm_unmap_aliases (3)
https://syzkaller.appspot.com/bug?extid=fe8f8efd070d727de971
<9> 571 Yes INFO: rcu detected stall in sys_openat (3)
https://syzkaller.appspot.com/bug?extid=23d96fb466ad56cbb5e5
<10> 529 Yes INFO: rcu detected stall in x64_sys_call
https://syzkaller.appspot.com/bug?extid=65203730e781d98f23a0
---
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-04-22 9:08 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=69e89013.a00a0220.17a17.0029.GAE@google.com \
--to=syzbot+listaebfd2e176cddedda623@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.