From: syzbot <syzbot+list282472007f650884ff12@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Nov 2023)
Date: Tue, 14 Nov 2023 19:00:22 -0800 [thread overview]
Message-ID: <000000000000a38a52060a281af5@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, 9 new issues were detected and 0 were fixed.
In total, 49 issues are still open and 237 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7353 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<2> 616 No KCSAN: data-race in generic_fillattr / shmem_mknod (2)
https://syzkaller.appspot.com/bug?extid=702361cf7e3d95758761
<3> 575 No KCSAN: data-race in generic_fillattr / shmem_unlink (3)
https://syzkaller.appspot.com/bug?extid=f682b67a78ce05867e78
<4> 272 Yes BUG: bad usercopy in fpa_set
https://syzkaller.appspot.com/bug?extid=cb76c2983557a07cdb14
<5> 131 No KCSAN: data-race in __filemap_remove_folio / folio_mapping (2)
https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
<6> 15 Yes memory leak in xas_create
https://syzkaller.appspot.com/bug?extid=a785d07959bc94837d51
<7> 10 Yes kernel BUG in do_page_mkwrite
https://syzkaller.appspot.com/bug?extid=cfba1abcb2cf7b39a320
<8> 4 Yes INFO: task hung in __unmap_and_move (4)
https://syzkaller.appspot.com/bug?extid=b7ad168b779385f8cd58
<9> 2 Yes BUG: unable to handle kernel paging request in __pte_offset_map_lock
https://syzkaller.appspot.com/bug?extid=89edd67979b52675ddec
<10> 1 Yes general protection fault in unlink_file_vma (2)
https://syzkaller.appspot.com/bug?extid=7fbdbd17a5bd6d01bc65
---
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:[~2023-11-15 3:00 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=000000000000a38a52060a281af5@google.com \
--to=syzbot+list282472007f650884ff12@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