From: syzbot <syzbot+listf2f28c8e4d5809654f88@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report
Date: Fri, 31 Mar 2023 08:01:51 -0700 [thread overview]
Message-ID: <00000000000032660805f8337db1@google.com> (raw)
Hello mm maintainers/developers,
This is a 30-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, 15 new issues were detected and 2 were fixed.
In total, 120 issues are still open and 197 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
1899 Yes WARNING in split_huge_page_to_list (2)
https://syzkaller.appspot.com/bug?extid=07a218429c8d19b1fb25
176 Yes INFO: task hung in do_read_cache_folio
https://syzkaller.appspot.com/bug?extid=be946efe33b2d9664348
92 Yes INFO: task hung in __filemap_get_folio
https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
52 Yes INFO: task hung in __lru_add_drain_all
https://syzkaller.appspot.com/bug?extid=a9b681dcbc06eb2bca04
38 Yes INFO: rcu detected stall in syscall_exit_to_user_mode (2)
https://syzkaller.appspot.com/bug?extid=a68ef3b1f46bc3aced5c
18 Yes kernel BUG in folio_end_writeback
https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
---
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.
next reply other threads:[~2023-03-31 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 15:01 syzbot [this message]
2023-04-06 9:37 ` Gang Li
2023-04-06 9:53 ` Aleksandr Nogikh
2023-04-06 10:02 ` Gang Li
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=00000000000032660805f8337db1@google.com \
--to=syzbot+listf2f28c8e4d5809654f88@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