public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yang, Sheng" <sheng.yang@intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: KVM: x86: verify MTRR/PAT validity
Date: Thu, 18 Jun 2009 10:39:32 +0800	[thread overview]
Message-ID: <200906181039.33205.sheng.yang@intel.com> (raw)
In-Reply-To: <20090616120529.GA529@amt.cnet>

On Tuesday 16 June 2009 20:05:29 Marcelo Tosatti wrote:
> Do not allow invalid MTRR/PAT values in set_msr_mtrr.
>
> Please review carefully.
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
Looks fine to me.

Is it necessary to check reserved bit of MSR_MTRRdefType and variable MTRRs as 
well? Maybe like this:

if (msr == MSR_MTRRdefType) {
	return valid_mtrr_type(data & ~0xc00ull);
}

And variable ones can be:

#define MTRR_VALID_MASK(v, msr) (~(rsvd_bits(cpuid_max_physaddr(v)) | ((msr % 
2) << 11)))

return valid_mtrr_type(data & MTRR_VALID_MASK(vcpu, msr)))


(rsvd_bits() is in mmu.c, both untested)

Maybe we can put cpuid_max_physaddr as a field in vcpu struct?

-- 
regards
Yang, Sheng

>
> Index: kvm/arch/x86/kvm/x86.c
> ===================================================================
> --- kvm.orig/arch/x86/kvm/x86.c
> +++ kvm/arch/x86/kvm/x86.c
> @@ -722,11 +722,53 @@ static bool msr_mtrr_valid(unsigned msr)
>  	return false;
>  }
>
> +static unsigned mtrr_types[] = {0, 1, 4, 5, 6};
> +static unsigned pat_types[] = {0, 1, 4, 5, 6, 7};
> +
> +static bool valid_mt(unsigned type, int len, unsigned array[len])
> +{
> +	int i;
> +
> +	for (i = 0; i < len; i++)
> +		if (type == array[i])
> +			return true;
> +
> +	return false;
> +}
> +
> +#define valid_pat_type(a) valid_mt(a, ARRAY_SIZE(pat_types), pat_types)
> +#define valid_mtrr_type(a) valid_mt(a, ARRAY_SIZE(mtrr_types), mtrr_types)
> +
> +static bool mtrr_valid(u32 msr, u64 data)
> +{
> +	int i;
> +
> +	if (!msr_mtrr_valid(msr))
> +		return false;
> +
> +	if (msr == MSR_IA32_CR_PAT) {
> +		for (i = 0; i < 8; i++)
> +			if (!valid_pat_type((data >> (i * 8)) & 0xff))
> +				return false;
> +		return true;
> +	} else if (msr == MSR_MTRRdefType) {
> +		return valid_mtrr_type(data & 0xff);
> +	} else if (msr >= MSR_MTRRfix64K_00000 && msr <= MSR_MTRRfix4K_F8000) {
> +		for (i = 0; i < 8 ; i++)
> +			if (!valid_mtrr_type((data >> (i * 8)) & 0xff))
> +				return false;
> +		return true;
> +	}
> +
> +	/* variable MTRRs, physmaskn have bits 0-10 reserved */
> +	return valid_mtrr_type(data & 0xff);
> +}
> +
>  static int set_msr_mtrr(struct kvm_vcpu *vcpu, u32 msr, u64 data)
>  {
>  	u64 *p = (u64 *)&vcpu->arch.mtrr_state.fixed_ranges;
>
> -	if (!msr_mtrr_valid(msr))
> +	if (!mtrr_valid(msr, data))
>  		return 1;
>
>  	if (msr == MSR_MTRRdefType) {



  reply	other threads:[~2009-06-18  2:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 12:05 KVM: x86: verify MTRR/PAT validity Marcelo Tosatti
2009-06-18  2:39 ` Yang, Sheng [this message]
2009-06-22 18:27   ` Marcelo Tosatti
2009-06-24 10:00     ` Avi Kivity
2009-06-18  9:00 ` Avi Kivity

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=200906181039.33205.sheng.yang@intel.com \
    --to=sheng.yang@intel.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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