From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: fix hypercall continuation cancellation in XENMAPSPACE_gmfn_range compat wrapper
Date: Wed, 28 Nov 2012 08:28:25 +0000 [thread overview]
Message-ID: <CCDB7BA9.4627B%keir.xen@gmail.com> (raw)
In-Reply-To: <50B5CECD02000078000ABF99@nat28.tlf.novell.com>
On 28/11/2012 07:43, "Jan Beulich" <JBeulich@suse.com> wrote:
> When no continuation was established, there must also not be an attempt
> to cancel it - hypercall_cancel_continuation(), in the non-HVM, non-
> multicall case, adjusts the guest mode return address in a way assuming
> that an earlier call hypercall_create_continuation() took place.
>
> Once touching this code, also restructure it slightly to improve
> readability and switch to using the more relaxed copy function (copying
> from the same guest memory already validated the virtual address
> range).
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/arch/x86/x86_64/compat/mm.c
> +++ b/xen/arch/x86/x86_64/compat/mm.c
> @@ -66,21 +66,20 @@ int compat_arch_memory_op(int op, XEN_GU
> XLAT_add_to_physmap(nat, &cmp);
> rc = arch_memory_op(op, guest_handle_from_ptr(nat, void));
>
> - if ( cmp.space == XENMAPSPACE_gmfn_range )
> + if ( !rc || cmp.space != XENMAPSPACE_gmfn_range )
> + break;
> +
> + XLAT_add_to_physmap(&cmp, nat);
> + if ( __copy_to_guest(arg, &cmp, 1) )
> {
> - if ( rc )
> - {
> - XLAT_add_to_physmap(&cmp, nat);
> - if ( copy_to_guest(arg, &cmp, 1) )
> - {
> - hypercall_cancel_continuation();
> - return -EFAULT;
> - }
> - }
> if ( rc == __HYPERVISOR_memory_op )
> - hypercall_xlat_continuation(NULL, 0x2, nat, arg);
> + hypercall_cancel_continuation();
> + return -EFAULT;
> }
>
> + if ( rc == __HYPERVISOR_memory_op )
> + hypercall_xlat_continuation(NULL, 0x2, nat, arg);
> +
> break;
> }
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-11-28 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 7:43 [PATCH] x86: fix hypercall continuation cancellation in XENMAPSPACE_gmfn_range compat wrapper Jan Beulich
2012-11-28 8:28 ` 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=CCDB7BA9.4627B%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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).