All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+lista19928a035a1d33d70b5@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Feb 2024)
Date: Sat, 17 Feb 2024 12:23:31 -0800	[thread overview]
Message-ID: <000000000000550c79061199a23f@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, 8 new issues were detected and 0 were fixed.
In total, 40 issues are still open and 224 have been fixed so far.

Some of the still happening issues:

Ref  Crashes Repro Title
<1>  135391  Yes   KMSAN: uninit-value in virtqueue_add (4)
                   https://syzkaller.appspot.com/bug?extid=d7521c1e3841ed075a42
<2>  7366    Yes   WARNING in ext4_dirty_folio
                   https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<3>  689     Yes   KCSAN: data-race in generic_fillattr / shmem_mknod (2)
                   https://syzkaller.appspot.com/bug?extid=702361cf7e3d95758761
<4>  645     Yes   BUG: bad usercopy in fpa_set
                   https://syzkaller.appspot.com/bug?extid=cb76c2983557a07cdb14
<5>  632     No    KCSAN: data-race in generic_fillattr / shmem_unlink (3)
                   https://syzkaller.appspot.com/bug?extid=f682b67a78ce05867e78
<6>  626     Yes   possible deadlock in filemap_fault
                   https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<7>  200     No    KCSAN: data-race in __filemap_remove_folio / folio_mapping (2)
                   https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
<8>  73      Yes   WARNING in __kfence_free (3)
                   https://syzkaller.appspot.com/bug?extid=59f37b0ab4c558a5357c
<9>  36      Yes   BUG: unable to handle kernel paging request in list_lru_add
                   https://syzkaller.appspot.com/bug?extid=2403e3909382fbdeaf6c
<10> 33      Yes   BUG: unable to handle kernel NULL pointer dereference in __kmap_local_page_prot
                   https://syzkaller.appspot.com/bug?extid=b18872ea9631b5dcef3b

---
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-02-17 20:23 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=000000000000550c79061199a23f@google.com \
    --to=syzbot+lista19928a035a1d33d70b5@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.