From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
David Woodhouse <dwmw2@infradead.org>,
Paul Durrant <paul@xen.org>, Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Pei Li <peili.dev@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
syzkaller-bugs@googlegroups.com, llvm@lists.linux.dev,
syzbot+fd555292a1da3180fc82@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] kvm: Fix warning in__kvm_gpc_refresh
Date: Fri, 28 Jun 2024 15:55:22 -0700 [thread overview]
Message-ID: <171961374413.228500.7729150745631933428.b4-ty@google.com> (raw)
In-Reply-To: <20240627-bug5-v2-1-2c63f7ee6739@gmail.com>
On Thu, 27 Jun 2024 08:03:56 -0700, Pei Li wrote:
> Check for invalid hva address stored in data and return -EINVAL before
> calling into __kvm_gpc_activate().
Applied to kvm-x86 fixes, thanks!
[1/1] kvm: Fix warning in__kvm_gpc_refresh
https://github.com/kvm-x86/linux/commit/ebbdf37ce9ab
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2024-06-28 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 15:03 Pei Li
2024-06-28 14:25 ` Paul Durrant
2024-06-28 15:00 ` David Woodhouse
2024-06-28 22:55 ` 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=171961374413.228500.7729150745631933428.b4-ty@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=peili.dev@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+fd555292a1da3180fc82@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®