public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: "'Marek Marczykowski-Górecki'" <marmarek@invisiblethingslab.com>
Cc: "Juergen Groß" <jgross@suse.com>,
	"Andrew Cooper" <Andrew.Cooper3@citrix.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>
Subject: RE: [Xen-devel] [PATCH] x86/xen: allow userspace access during hypercalls
Date: Mon, 26 Jun 2017 13:24:55 +0000	[thread overview]
Message-ID: <6a2c9fea81ef4e4ba7d533dba604223b@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20170626132157.GW1268@mail-itl>

> -----Original Message-----
> From: 'Marek Marczykowski-Górecki'
> [mailto:marmarek@invisiblethingslab.com]
> Sent: 26 June 2017 14:22
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Juergen Groß <jgross@suse.com>; Andrew Cooper
> <Andrew.Cooper3@citrix.com>; x86@kernel.org; linux-
> kernel@vger.kernel.org; stable@vger.kernel.org; xen-
> devel@lists.xenproject.org; Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Subject: Re: [Xen-devel] [PATCH] x86/xen: allow userspace access during
> hypercalls
> 
> On Mon, Jun 26, 2017 at 01:09:58PM +0000, Paul Durrant wrote:
> > > -----Original Message-----
> > > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of
> > > Marek Marczykowski-Górecki
> > > Sent: 26 June 2017 13:45
> > > To: Juergen Groß <jgross@suse.com>
> > > Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>; x86@kernel.org;
> linux-
> > > kernel@vger.kernel.org; stable@vger.kernel.org; xen-
> > > devel@lists.xenproject.org; Boris Ostrovsky
> <boris.ostrovsky@oracle.com>
> > > Subject: Re: [Xen-devel] [PATCH] x86/xen: allow userspace access during
> > > hypercalls
> > >
> > > On Mon, Jun 26, 2017 at 02:05:48PM +0200, Juergen Groß wrote:
> > > > On 06/23/2017 02:47 PM, Marek Marczykowski-Górecki wrote:
> > > > > Userspace application can do a hypercall through /dev/xen/privcmd,
> and
> > > > > some for some hypercalls argument is a pointers to user-provided
> > > > > structure. When SMAP is supported and enabled, hypervisor can't
> access.
> > > > > So, lets allow it.
> > > >
> > > > What about HYPERVISOR_dm_op?
> > >
> > > Indeed, arguments copied to kernel space there are only addresses of
> > > buffers. Will send v2 in a moment.
> > > But I can't test it right now, as for my understanding this require
> > > HVM/PVHv2 dom0 or stubdomain...
> > >
> >
> > No, you don't need anything particularly special to use dm_op. Just up-to-
> date xen, privcmd, and QEMU. QEMU should end up using dm_op by default
> if all three are in place.
> 
> But the issue this patch fixes applies only to hypercalls issued from HVM.

Oh, I see what you mean. Well I guess you could manually run QEMU from an HVM domain, but it would be a bit of a faff to set up.

  Paul

> 
> --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?

      reply	other threads:[~2017-06-26 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 12:47 [PATCH] x86/xen: allow userspace access during hypercalls Marek Marczykowski-Górecki
2017-06-26 12:05 ` Juergen Groß
2017-06-26 12:45   ` Marek Marczykowski-Górecki
2017-06-26 12:49     ` [PATCH v2] " Marek Marczykowski-Górecki
2017-06-26 12:54       ` Juergen Groß
2017-07-03 11:28       ` Juergen Gross
2017-06-26 13:09     ` [Xen-devel] [PATCH] " Paul Durrant
2017-06-26 13:21       ` 'Marek Marczykowski-Górecki'
2017-06-26 13:24         ` Paul Durrant [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=6a2c9fea81ef4e4ba7d533dba604223b@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marmarek@invisiblethingslab.com \
    --cc=stable@vger.kernel.org \
    --cc=x86@kernel.org \
    --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