All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: KVM: x86: use proper port value when checking io instruction permission
Date: Tue, 24 May 2011 22:07:48 +0300	[thread overview]
Message-ID: <4DDC0204.9050002@redhat.com> (raw)
In-Reply-To: <20110524172706.GC22042@redhat.com>

On 05/24/2011 08:27 PM, Gleb Natapov wrote:
> On Tue, May 24, 2011 at 02:11:20PM -0300, Marcelo Tosatti wrote:
> >
> >  Commit fa4491a6b667304 moved the permission check for io instructions
> >  to the ->check_perm callback. It failed to copy the port value from RDX
> >  register for string and "in,out ax,dx" instructions. Fix it.
> >
> >  Fixes FC8.32 installation.

Ouch.


> >  @@ -2955,6 +2964,15 @@ static int check_perm_out(struct x86_emulate_ctxt *ctxt)
> >   {
> >   	struct decode_cache *c =&ctxt->decode;
> >
> >  +	switch (c->b) {
> >  +	case 0x6e: /* outsb */
> >  +	case 0x6f: /* outsw/outsd */
> >  +	case 0xee: /* out dx,al */
> >  +	case 0xef: /* out dx,(e/r)ax */
> >  +		c->dst.val = c->regs[VCPU_REGS_RDX];
> >  +		break;
> >  +	}
> >  +
> >   	c->src.bytes = min(c->src.bytes, 4u);
> >   	if (!emulator_io_permited(ctxt, c->dst.val, c->src.bytes))
> >   		return emulate_gp(ctxt, 0);
> I'd rather do it at decoding stage by adding SrcDX/DstDX.
>

Note we haven't decoded operands yet.  And this doesn't fix in $imm8, %al.

Maybe we need an additional check site after operands are fetched.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2011-05-24 19:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 17:11 KVM: x86: use proper port value when checking io instruction permission Marcelo Tosatti
2011-05-24 17:27 ` Gleb Natapov
2011-05-24 19:07   ` Avi Kivity [this message]
2011-05-24 19:18     ` Gleb Natapov
2011-05-24 19:25       ` Avi Kivity
2011-05-25 18:18   ` KVM: x86: use proper port value when checking io instruction permission (v2) Marcelo Tosatti
2011-05-26  6:31     ` Avi Kivity
2011-05-26  6:55       ` Gleb Natapov
2011-05-26  7:02         ` Avi Kivity
2011-05-26  7:04           ` Avi Kivity
2011-05-26  7:07             ` Gleb Natapov
2011-05-26  7:49               ` Paolo Bonzini
2011-05-26  8:26                 ` Gleb Natapov
2011-05-26  9:00                   ` Paolo Bonzini
2011-05-26  9:02                     ` Gleb Natapov
2011-05-26  9:23                       ` Paolo Bonzini
2011-05-26  9:29                         ` Gleb Natapov
2011-05-26 10:43                 ` Marcelo Tosatti
2011-05-26 11:56       ` KVM: x86: use proper port value when checking io instruction permission (v3) Marcelo Tosatti
2011-05-29  8:34         ` Avi Kivity
2011-05-30 18:23           ` KVM: x86: use proper port value when checking io instruction permission (v4) Marcelo Tosatti
2011-05-30 18:28             ` Avi Kivity
2011-05-30 18:23           ` KVM: x86: use proper port value when checking io instruction permission (v3) Marcelo Tosatti

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=4DDC0204.9050002@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=joerg.roedel@amd.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 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.