From: Jan Kiszka <jan.kiszka@siemens.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-stable@nongnu.org, qemu-ppc@nongnu.org, agraf@suse.de,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] pseries: Synchronize qemu and KVM state on hypercalls
Date: Thu, 20 Sep 2012 09:39:56 +0200 [thread overview]
Message-ID: <505AC84C.9060500@siemens.com> (raw)
In-Reply-To: <1348124922-24263-2-git-send-email-david@gibson.dropbear.id.au>
On 2012-09-20 09:08, David Gibson wrote:
> Currently the KVM exit path for PAPR hypercalls does not synchronize the
> qemu cpu state with the KVM state. Mostly this works, because the actual
> hypercall arguments and return values are explicitly passed through the
> kvm_run structure. However, the hypercall path includes a privilege check,
> to ensure that only the guest kernel can invoke hypercalls, not the guest
> userspace. Because of the lack of sync, this privilege check will use an
> out of date copy of the MSR, which could lead either to guest userspace
> being able to invoke hypercalls (a security hole for the guest) or to the
> guest kernel being incorrectly refused privilege leading to various other
> failures.
>
> This patch fixes the bug by forcing a synchronization on the hypercall exit
> path. This does mean we have a potentially quite expensive get and set of
> the state, however performance critical hypercalls are generally already
> implemented inside KVM so this probably won't matter. If it is a
> performance problem we can optimize it later by having the kernel perform
> the privilege check. That will need a new capability, however, since qemu
> will still need the privilege check for older kernels.
If it's just about reading a small subset of the state (a single MSR?)
to allow the privilege check, you can also open-code only that in HCALL
exit. If it really matters.
Jan
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> target-ppc/kvm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
> index 546c116..78a47fb 100644
> --- a/target-ppc/kvm.c
> +++ b/target-ppc/kvm.c
> @@ -813,6 +813,7 @@ int kvm_arch_handle_exit(CPUPPCState *env, struct kvm_run *run)
> #ifdef CONFIG_PSERIES
> case KVM_EXIT_PAPR_HCALL:
> dprintf("handle PAPR hypercall\n");
> + cpu_synchronize_state(env);
> run->papr_hcall.ret = spapr_hypercall(env, run->papr_hcall.nr,
> run->papr_hcall.args);
> ret = 0;
>
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-09-20 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 7:08 [Qemu-devel] [0/2] Bugfixes for ppc KVM David Gibson
2012-09-20 7:08 ` [Qemu-devel] [PATCH 1/2] pseries: Synchronize qemu and KVM state on hypercalls David Gibson
2012-09-20 7:38 ` Alexander Graf
2012-09-20 11:53 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-09-20 12:44 ` Alexander Graf
2012-09-21 0:22 ` David Gibson
2012-09-24 14:27 ` Alexander Graf
2012-09-25 7:05 ` David Gibson
2012-09-20 7:39 ` Jan Kiszka [this message]
2012-09-20 11:54 ` David Gibson
2012-09-20 7:08 ` [Qemu-devel] [PATCH 2/2] target-ppc: KVM: Fix some kernel version edge cases for kvmppc_reset_htab() David Gibson
2012-09-20 8:58 ` Alexander Graf
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=505AC84C.9060500@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-stable@nongnu.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 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.