Linux-Modules Archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+lista106f8f60124dc0eda6e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
	mcgrof@kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly modules report (Jul 2023)
Date: Wed, 19 Jul 2023 02:03:09 -0700	[thread overview]
Message-ID: <000000000000f03d270600d34c07@google.com> (raw)

Hello modules maintainers/developers,

This is a 31-day syzbot report for the modules subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/modules

During the period, 3 new issues were detected and 1 were fixed.
In total, 3 issues are still open and 5 have been fixed so far.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 337     Yes   KASAN: invalid-access Read in init_module_from_file
                  https://syzkaller.appspot.com/bug?extid=e3705186451a87fd93b8
<2> 84      Yes   general protection fault in sys_finit_module
                  https://syzkaller.appspot.com/bug?extid=9e4e94a2689427009d35
<3> 10      Yes   WARNING in do_page_fault
                  https://syzkaller.appspot.com/bug?extid=78c0d2c0b793eabb450d

---
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-07-19  9:03 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=000000000000f03d270600d34c07@google.com \
    --to=syzbot+lista106f8f60124dc0eda6e@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).