From: syzbot <syzbot+list477ead9e37a715bd2178@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Sep 2025)
Date: Sun, 14 Sep 2025 23:54:26 -0700 [thread overview]
Message-ID: <68c7b822.050a0220.2ff435.038d.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 2 were fixed.
In total, 117 issues are still open and 340 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7424 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<2> 5478 Yes WARNING in v9fs_fid_get_acl
https://syzkaller.appspot.com/bug?extid=a83dc51a78f0f4cf20da
<3> 3643 Yes INFO: task hung in page_cache_ra_unbounded (2)
https://syzkaller.appspot.com/bug?extid=265e1cae90f8fa08f14d
<4> 2919 Yes possible deadlock in filemap_fault
https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<5> 822 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<6> 708 No KCSAN: data-race in __filemap_remove_folio / folio_mapping (2)
https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
<7> 580 Yes INFO: task hung in _vm_unmap_aliases (3)
https://syzkaller.appspot.com/bug?extid=fe8f8efd070d727de971
<8> 556 Yes INFO: rcu detected stall in addrconf_rs_timer (6)
https://syzkaller.appspot.com/bug?extid=fecf8bd19c1f78edb255
<9> 464 Yes kernel BUG in filemap_unaccount_folio
https://syzkaller.appspot.com/bug?extid=17a207d226b8a5fb0fd9
<10> 457 Yes INFO: rcu detected stall in sys_newfstatat (4)
https://syzkaller.appspot.com/bug?extid=1c02a56102605204445c
---
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:[~2025-09-15 6:54 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=68c7b822.050a0220.2ff435.038d.GAE@google.com \
--to=syzbot+list477ead9e37a715bd2178@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.