From: syzbot <syzbot+list9b272dba49b70afcd21e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (May 2024)
Date: Thu, 30 May 2024 23:48:31 -0700 [thread overview]
Message-ID: <0000000000002bbe460619ba5f40@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 1 were fixed.
In total, 56 issues are still open and 242 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 10236 Yes KASAN: slab-out-of-bounds Read in generic_perform_write
https://syzkaller.appspot.com/bug?extid=4a2376bc62e59406c414
<2> 7377 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<3> 1078 Yes possible deadlock in filemap_fault
https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<4> 720 Yes KCSAN: data-race in generic_fillattr / shmem_mknod (2)
https://syzkaller.appspot.com/bug?extid=702361cf7e3d95758761
<5> 466 Yes inconsistent lock state in __mmap_lock_do_trace_acquire_returned
https://syzkaller.appspot.com/bug?extid=76f802bc1dee8ba28a6e
<6> 390 Yes WARNING in kunmap_local_indexed
https://syzkaller.appspot.com/bug?extid=691cb37358791bebebe6
<7> 93 Yes BUG: unable to handle kernel NULL pointer dereference in __kmap_local_page_prot
https://syzkaller.appspot.com/bug?extid=b18872ea9631b5dcef3b
<8> 72 No INFO: task hung in __lru_add_drain_all (2)
https://syzkaller.appspot.com/bug?extid=5294aa7d73bb0fa85bd0
<9> 49 Yes BUG: unable to handle kernel paging request in list_lru_add
https://syzkaller.appspot.com/bug?extid=2403e3909382fbdeaf6c
<10> 46 Yes INFO: rcu detected stall in sys_openat (3)
https://syzkaller.appspot.com/bug?extid=23d96fb466ad56cbb5e5
---
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-05-31 6:48 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=0000000000002bbe460619ba5f40@google.com \
--to=syzbot+list9b272dba49b70afcd21e@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.