diff options
| author |   Juergen Gross <jgross@suse.com> | 2018-06-13 11:58:06 +0200 |
|---|---|---|
| committer |   Boris Ostrovsky <boris.ostrovsky@oracle.com> | 2018-08-07 11:37:01 -0400 |
| commit | cd9139220b87f40ea83858de1d6436c639376ce7 (patch) | |
| tree | 3f6e21d752354b5773dc6289246206498094a10d /arch/x86/xen | |
| parent | xen/pv: Call get_cpu_address_sizes to set x86_virt/phys_bits (diff) | |
| download | wireguard-linux-cd9139220b87f40ea83858de1d6436c639376ce7.tar.xz wireguard-linux-cd9139220b87f40ea83858de1d6436c639376ce7.zip | |
xen: don't use privcmd_call() from xen_mc_flush()
Using privcmd_call() for a singleton multicall seems to be wrong, as
privcmd_call() is using stac()/clac() to enable hypervisor access to
Linux user space.
Even if currently not a problem (pv domains can't use SMAP while HVM
and PVH domains can't use multicalls) things might change when
PVH dom0 support is added to the kernel.
Reported-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Diffstat (limited to 'arch/x86/xen')
| -rw-r--r-- | arch/x86/xen/multicalls.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/arch/x86/xen/multicalls.c b/arch/x86/xen/multicalls.c index dc502ca8263e..2bce7958ce8b 100644 --- a/arch/x86/xen/multicalls.c +++ b/arch/x86/xen/multicalls.c @@ -80,9 +80,9 @@ void xen_mc_flush(void) and just do the call directly. */ mc = &b->entries[0]; - mc->result = privcmd_call(mc->op, - mc->args[0], mc->args[1], mc->args[2], - mc->args[3], mc->args[4]); + mc->result = xen_single_call(mc->op, mc->args[0], mc->args[1], + mc->args[2], mc->args[3], + mc->args[4]); ret = mc->result < 0; break; |