From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+ead0473557070d5432cd@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.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] memory leak in kvm_vcpu_ioctl_set_cpuid2
Date: Wed, 26 Jan 2022 20:07:33 +0000 [thread overview]
Message-ID: <YfGqBUYWj6nBxntP@google.com> (raw)
In-Reply-To: <000000000000be3e4505d681aa17@google.com>
On Wed, Jan 26, 2022, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 0809edbae347 Merge tag 'devicetree-fixes-for-5.17-1' of gi..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17982967b00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=cc8d6c95ce1d56de
> dashboard link: https://syzkaller.appspot.com/bug?extid=ead0473557070d5432cd
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1402f91fb00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ba591fb00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+ead0473557070d5432cd@syzkaller.appspotmail.com
#syz fix: KVM: x86: Free kvm_cpuid_entry2 array on post-KVM_RUN KVM_SET_CPUID{,2}
prev parent reply other threads:[~2022-01-26 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 20:01 [syzbot] memory leak in kvm_vcpu_ioctl_set_cpuid2 syzbot
2022-01-26 20:07 ` 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=YfGqBUYWj6nBxntP@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.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+ead0473557070d5432cd@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 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.