From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Juergen Groß" <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/xen: allow userspace access during hypercalls
Date: Mon, 26 Jun 2017 14:45:05 +0200 [thread overview]
Message-ID: <20170626124505.GV1268@mail-itl> (raw)
In-Reply-To: <6f8113d8-10a2-b23f-16c1-8b97b2fba0bb@suse.com>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
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...
--
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-06-26 12:45 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 [this message]
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
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=20170626124505.GV1268@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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