From: Julien Grall <julien@xen.org>
To: Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH] common: don't require use of DOMID_SELF
Date: Thu, 14 Jan 2021 14:43:11 +0000 [thread overview]
Message-ID: <6b80d9bd-58a1-0854-2ff9-7153ddecae26@xen.org> (raw)
In-Reply-To: <72c9f0ec-81e3-63f9-2513-46e463642219@suse.com>
Hi Jan,
On 14/01/2021 14:02, Jan Beulich wrote:
> It's not overly difficult for a domain to figure out its ID, so
> requiring the use of DOMID_SELF in a very limited set of places isn't
> really helpful towards keeping the ID opaque to the guest.
So I agree that a domid can be figured out really easily today and in
principle it would be fine to relax it.
However, most of the guest OSes will care about running on older Xen
versions. Therefore they are not going to be able to use this relaxation.
So I am not entirely convinced the relaxation is actually worth it for
existing hypercalls.
Anyway, if we decide to relax it, then I think we should update the
public headers because an OS using this relaxation will not work on
older Xen. A developper will not be able to know that without looking at
the implementation.
Cheers,
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/common/grant_table.c
> +++ b/xen/common/grant_table.c
> @@ -2776,15 +2776,19 @@ struct gnttab_copy_buf {
> static int gnttab_copy_lock_domain(domid_t domid, bool is_gref,
> struct gnttab_copy_buf *buf)
> {
> - /* Only DOMID_SELF may reference via frame. */
> - if ( domid != DOMID_SELF && !is_gref )
> - return GNTST_permission_denied;
> -
> buf->domain = rcu_lock_domain_by_any_id(domid);
>
> if ( !buf->domain )
> return GNTST_bad_domain;
>
> + /* Only the local domain may reference via frame. */
> + if ( buf->domain != current->domain && !is_gref )
> + {
> + rcu_unlock_domain(buf->domain);
> + buf->domain = NULL;
> + return GNTST_permission_denied;
> + }
> +
> buf->ptr.domid = domid;
>
> return GNTST_okay;
> --- a/xen/common/page_alloc.c
> +++ b/xen/common/page_alloc.c
> @@ -2566,13 +2566,7 @@ __initcall(register_heap_trigger);
>
> struct domain *get_pg_owner(domid_t domid)
> {
> - struct domain *pg_owner = NULL, *curr = current->domain;
> -
> - if ( unlikely(domid == curr->domain_id) )
> - {
> - gdprintk(XENLOG_WARNING, "Cannot specify itself as foreign domain\n");
> - goto out;
> - }
> + struct domain *pg_owner;
>
> switch ( domid )
> {
> @@ -2590,7 +2584,6 @@ struct domain *get_pg_owner(domid_t domi
> break;
> }
>
> - out:
> return pg_owner;
> }
>
>
--
Julien Grall
next prev parent reply other threads:[~2021-01-14 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 14:02 [PATCH] common: don't require use of DOMID_SELF Jan Beulich
2021-01-14 14:43 ` Julien Grall [this message]
2021-01-14 15:30 ` Jan Beulich
2021-01-14 15:36 ` Andrew Cooper
2021-01-15 9:59 ` Julien Grall
2021-01-15 10:22 ` Jan Beulich
2021-01-14 15:01 ` Andrew Cooper
2021-01-14 15:38 ` Jan Beulich
2021-01-15 10:49 ` Jan Beulich
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=6b80d9bd-58a1-0854-2ff9-7153ddecae26@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.