From: syzbot <syzbot+liste8e8a93665e01bff6e87@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Oct 2024)
Date: Thu, 03 Oct 2024 02:02:22 -0700 [thread overview]
Message-ID: <66fe5d9e.050a0220.28a3b.020d.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 4 were fixed.
In total, 79 issues are still open and 263 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 10299 Yes KASAN: slab-out-of-bounds Read in generic_perform_write
https://syzkaller.appspot.com/bug?extid=4a2376bc62e59406c414
<2> 7383 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<3> 2612 Yes INFO: task hung in page_cache_ra_unbounded (2)
https://syzkaller.appspot.com/bug?extid=265e1cae90f8fa08f14d
<4> 2189 Yes INFO: rcu detected stall in worker_thread (9)
https://syzkaller.appspot.com/bug?extid=225bfad78b079744fd5e
<5> 1579 Yes possible deadlock in filemap_fault
https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<6> 679 Yes possible deadlock in gup_fast_fallback
https://syzkaller.appspot.com/bug?extid=63ba90b81c16b86379bd
<7> 559 Yes INFO: rcu detected stall in corrupted (4)
https://syzkaller.appspot.com/bug?extid=aa7d098bd6fa788fae8e
<8> 460 Yes INFO: task hung in _vm_unmap_aliases (3)
https://syzkaller.appspot.com/bug?extid=fe8f8efd070d727de971
<9> 289 No KCSAN: data-race in __filemap_remove_folio / folio_mapping (2)
https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
<10> 287 No WARNING: locking bug in __schedule
https://syzkaller.appspot.com/bug?extid=46b40e354b532433eeef
---
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:[~2024-10-03 9:02 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=66fe5d9e.050a0220.28a3b.020d.GAE@google.com \
--to=syzbot+liste8e8a93665e01bff6e87@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