public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+listf42719d660fa6d59a79a@syzkaller.appspotmail.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly kvm report (Jul 2023)
Date: Mon, 10 Jul 2023 02:35:42 -0700	[thread overview]
Message-ID: <000000000000c7224e06001eb4b1@google.com> (raw)

Hello kvm maintainers/developers,

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

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

Some of the still happening issues:

Ref Crashes Repro Title
<1> 138     Yes   WARNING in kvm_arch_vcpu_ioctl_run (5)
                  https://syzkaller.appspot.com/bug?extid=5feef0b9ee9c8e9e5689
<2> 89      Yes   WARNING in handle_exception_nmi (2)
                  https://syzkaller.appspot.com/bug?extid=4688c50a9c8e68e7aaa1
<3> 58      No    WARNING in kthread_bind_mask
                  https://syzkaller.appspot.com/bug?extid=087b7effddeec0697c66

---
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-10  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  9:35 syzbot [this message]
2023-07-10 20:28 ` [syzbot] Monthly kvm report (Jul 2023) Sean Christopherson

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=000000000000c7224e06001eb4b1@google.com \
    --to=syzbot+listf42719d660fa6d59a79a@syzkaller.appspotmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.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