From: "Juergen Groß" <jgross@suse.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org
Cc: 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 v2] x86/xen: allow userspace access during hypercalls
Date: Mon, 26 Jun 2017 14:54:07 +0200 [thread overview]
Message-ID: <664ecd67-8bd5-3efd-4b59-eef79640ef4c@suse.com> (raw)
In-Reply-To: <1498481386-8704-1-git-send-email-marmarek@invisiblethingslab.com>
On 06/26/2017 02:49 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.
>
> The same applies to HYPERVISOR_dm_op, where additionally privcmd driver
> carefully verify buffer addresses.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Thanks,
Juergen
next prev parent reply other threads:[~2017-06-26 12:54 UTC|newest]
Thread overview: 17+ 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:49 ` Marek Marczykowski-Górecki
2017-06-26 12:54 ` Juergen Groß [this message]
2017-06-26 12:54 ` Juergen Groß
2017-07-03 11:28 ` Juergen Gross
2017-07-03 11:28 ` Juergen Gross
2017-06-26 13:09 ` [PATCH] " Paul Durrant
2017-06-26 13:09 ` [Xen-devel] " Paul Durrant
2017-06-26 13:21 ` 'Marek Marczykowski-Górecki'
2017-06-26 13:24 ` Paul Durrant
2017-06-26 13:24 ` Paul Durrant
2017-06-26 13:21 ` 'Marek Marczykowski-Górecki'
2017-06-26 12:45 ` Marek Marczykowski-Górecki
2017-06-26 12:05 ` Juergen Groß
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=664ecd67-8bd5-3efd-4b59-eef79640ef4c@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.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 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.