From: syzbot <syzbot+list48ce08ed778c7a25633f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly mm report (Jan 2024)
Date: Wed, 17 Jan 2024 01:21:20 -0800 [thread overview]
Message-ID: <00000000000020a118060f20c5f3@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, 2 new issues were detected and 3 were fixed.
In total, 34 issues are still open and 223 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7363 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<2> 607 No KCSAN: data-race in generic_fillattr / shmem_unlink (3)
https://syzkaller.appspot.com/bug?extid=f682b67a78ce05867e78
<3> 489 Yes BUG: bad usercopy in fpa_set
https://syzkaller.appspot.com/bug?extid=cb76c2983557a07cdb14
<4> 55 Yes WARNING in __kfence_free (3)
https://syzkaller.appspot.com/bug?extid=59f37b0ab4c558a5357c
<5> 27 Yes BUG: unable to handle kernel paging request in list_lru_add
https://syzkaller.appspot.com/bug?extid=2403e3909382fbdeaf6c
<6> 24 Yes BUG: unable to handle kernel NULL pointer dereference in __kmap_local_page_prot
https://syzkaller.appspot.com/bug?extid=b18872ea9631b5dcef3b
<7> 11 No WARNING in __gup_longterm_locked (2)
https://syzkaller.appspot.com/bug?extid=f2577d8071a92e596253
<8> 11 Yes kernel BUG in do_page_mkwrite
https://syzkaller.appspot.com/bug?extid=cfba1abcb2cf7b39a320
<9> 8 Yes kernel BUG in filemap_unaccount_folio
https://syzkaller.appspot.com/bug?extid=17a207d226b8a5fb0fd9
<10> 6 Yes INFO: rcu detected stall in dput (8)
https://syzkaller.appspot.com/bug?extid=eb9f416500ff134ab699
---
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-01-17 9:21 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=00000000000020a118060f20c5f3@google.com \
--to=syzbot+list48ce08ed778c7a25633f@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;
as well as URLs for NNTP newsgroup(s).