From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/HVM: linear address must be canonical for the whole accessed range
Date: Fri, 20 Sep 2013 16:30:02 +0100 [thread overview]
Message-ID: <CE62288A.33FAC%keir.xen@gmail.com> (raw)
In-Reply-To: <523C64CA02000078000F4EE7@nat28.tlf.novell.com>
On 20/09/2013 14:07, "Jan Beulich" <JBeulich@suse.com> wrote:
> ... rather than just for the first byte.
>
> While at it, also
> - make the real mode case at least dpo a wrap around check
> - drop the mis-named "gpf" label (we're not generating faults here)
> and use in-place returns instead
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -1931,8 +1931,7 @@ int hvm_virtual_to_linear_addr(
> unsigned int addr_size,
> unsigned long *linear_addr)
> {
> - unsigned long addr = offset;
> - uint32_t last_byte;
> + unsigned long addr = offset, last_byte;
>
> if ( !(current->arch.hvm_vcpu.guest_cr[0] & X86_CR0_PE) )
> {
> @@ -1941,6 +1940,9 @@ int hvm_virtual_to_linear_addr(
> * Certain of them are not done in native real mode anyway.
> */
> addr = (uint32_t)(addr + reg->base);
> + last_byte = (uint32_t)addr + bytes - 1;
> + if ( last_byte < addr )
> + return 0;
> }
> else if ( addr_size != 64 )
> {
> @@ -1952,17 +1954,17 @@ int hvm_virtual_to_linear_addr(
> {
> case hvm_access_read:
> if ( (reg->attr.fields.type & 0xa) == 0x8 )
> - goto gpf; /* execute-only code segment */
> + return 0; /* execute-only code segment */
> break;
> case hvm_access_write:
> if ( (reg->attr.fields.type & 0xa) != 0x2 )
> - goto gpf; /* not a writable data segment */
> + return 0; /* not a writable data segment */
> break;
> default:
> break;
> }
>
> - last_byte = offset + bytes - 1;
> + last_byte = (uint32_t)offset + bytes - 1;
>
> /* Is this a grows-down data segment? Special limit check if so. */
> if ( (reg->attr.fields.type & 0xc) == 0x4 )
> @@ -1973,10 +1975,10 @@ int hvm_virtual_to_linear_addr(
>
> /* Check first byte and last byte against respective bounds. */
> if ( (offset <= reg->limit) || (last_byte < offset) )
> - goto gpf;
> + return 0;
> }
> else if ( (last_byte > reg->limit) || (last_byte < offset) )
> - goto gpf; /* last byte is beyond limit or wraps 0xFFFFFFFF */
> + return 0; /* last byte is beyond limit or wraps 0xFFFFFFFF */
>
> /*
> * Hardware truncates to 32 bits in compatibility mode.
> @@ -1993,15 +1995,14 @@ int hvm_virtual_to_linear_addr(
> if ( (seg == x86_seg_fs) || (seg == x86_seg_gs) )
> addr += reg->base;
>
> - if ( !is_canonical_address(addr) )
> - goto gpf;
> + last_byte = addr + bytes - 1;
> + if ( !is_canonical_address(addr) || last_byte < addr ||
> + !is_canonical_address(last_byte) )
> + return 0;
> }
>
> *linear_addr = addr;
> return 1;
> -
> - gpf:
> - return 0;
> }
>
> /* On non-NULL return, we leave this function holding an additional
>
>
>
prev parent reply other threads:[~2013-09-20 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 13:07 [PATCH] x86/HVM: linear address must be canonical for the whole accessed range Jan Beulich
2013-09-20 15:30 ` Keir Fraser [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=CE62288A.33FAC%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).