From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+d6d011bc17bb751d4aa2@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, glider@google.com,
hpa@zytor.com, jarkko@kernel.org, jmattson@google.com,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: [syzbot] KMSAN: uninit-value in kvm_cpuid
Date: Fri, 1 Oct 2021 15:13:14 +0000 [thread overview]
Message-ID: <YVclio5ny4ziKQer@google.com> (raw)
In-Reply-To: <00000000000048342f05cd44efc0@google.com>
On Thu, Sep 30, 2021, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: cd2c05533838 DO-NOT-SUBMIT: kmsan: suppress a report in ke..
> git tree: https://github.com/google/kmsan.git master
> console output: https://syzkaller.appspot.com/x/log.txt?x=11373b17300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=978f1b2d7a5aad3e
> dashboard link: https://syzkaller.appspot.com/bug?extid=d6d011bc17bb751d4aa2
> compiler: clang version 14.0.0 (git@github.com:llvm/llvm-project.git 0996585c8e3b3d409494eb5f1cad714b9e1f7fb5), GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b6c4cb300000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10fdb00f300000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d6d011bc17bb751d4aa2@syzkaller.appspotmail.com
#syz fix: KVM: x86: Swap order of CPUID entry "index" vs. "significant flag" checks
prev parent reply other threads:[~2021-10-01 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 6:47 [syzbot] KMSAN: uninit-value in kvm_cpuid syzbot
2021-10-01 15:13 ` Sean Christopherson [this message]
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=YVclio5ny4ziKQer@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=syzbot+d6d011bc17bb751d4aa2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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).