From: Eric Biggers <ebiggers3@gmail.com>
To: Tianyu Lan <lantianyu1986@gmail.com>
Cc: Tianyu Lan <Tianyu.Lan@microsoft.com>,
pbonzini@redhat.com, rkrcmar@redhat.com, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
jeremi.piotrowski@gmail.com
Subject: Re: [Resend Patch] KVM/x86: Fix wrong macro references of X86_CR0_PG_BIT and X86_CR4_PAE_BIT in kvm_valid_sregs()
Date: Thu, 18 Jan 2018 10:39:04 -0800 [thread overview]
Message-ID: <20180118183904.3fxeyfuyzlumgtrt@gmail.com> (raw)
In-Reply-To: <1516095247-21414-1-git-send-email-Tianyu.Lan@microsoft.com>
On Tue, Jan 16, 2018 at 05:34:07PM +0800, Tianyu Lan wrote:
> kvm_valid_sregs() should use X86_CR0_PG and X86_CR4_PAE to check bit
> status rather than X86_CR0_PG_BIT and X86_CR4_PAE_BIT. This patch is
> to fix it.
>
> Fixes: f29810335965a(KVM/x86: Check input paging mode when cs.l is set)
> Reported-by: Jeremi Piotrowski <jeremi.piotrowski@gmail.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Signed-off-by: Tianyu Lan <Tianyu.Lan@microsoft.com>
> ---
> Sorry for noise. Missed kvm maillist.
>
> arch/x86/kvm/x86.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 1cec2c6..c53298d 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -7496,13 +7496,13 @@ EXPORT_SYMBOL_GPL(kvm_task_switch);
>
> int kvm_valid_sregs(struct kvm_vcpu *vcpu, struct kvm_sregs *sregs)
> {
> - if ((sregs->efer & EFER_LME) && (sregs->cr0 & X86_CR0_PG_BIT)) {
> + if ((sregs->efer & EFER_LME) && (sregs->cr0 & X86_CR0_PG)) {
> /*
> * When EFER.LME and CR0.PG are set, the processor is in
> * 64-bit mode (though maybe in a 32-bit code segment).
> * CR4.PAE and EFER.LMA must be set.
> */
> - if (!(sregs->cr4 & X86_CR4_PAE_BIT)
> + if (!(sregs->cr4 & X86_CR4_PAE)
> || !(sregs->efer & EFER_LMA))
> return -EINVAL;
> } else {
> --
> 2.7.4
>
I came across this too and was just about to send the exact same patch. It
looks good to me as long as the bits it's supposed to be checking were correct
in the first place. Patch title could maybe be shortened a bit, e.g. "KVM/x86:
Fix references to CR0.PG and CR4.PAE in kvm_valid_sregs()". The "Fixes:" line
is also formatted incorrectly.
Thanks,
Eric
next prev parent reply other threads:[~2018-01-18 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 9:34 Tianyu Lan
2018-01-18 18:39 ` Eric Biggers [this message]
2018-01-19 2:41 ` Lan Tianyu
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=20180118183904.3fxeyfuyzlumgtrt@gmail.com \
--to=ebiggers3@gmail.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=hpa@zytor.com \
--cc=jeremi.piotrowski@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lantianyu1986@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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®