From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Xen-devel <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH] RFC XSM/evtchn: Never pretend to have successfully created a Xen event channel
Date: Mon, 12 Jan 2015 10:22:12 +0000 [thread overview]
Message-ID: <1421058132.26317.16.camel@citrix.com> (raw)
In-Reply-To: <1421056983-19328-1-git-send-email-andrew.cooper3@citrix.com>
On Mon, 2015-01-12 at 10:03 +0000, Andrew Cooper wrote:
> This is RFC because explicitly changes the logic introduced by c/s b34f2c375
> "xsm: label xen-consumer event channels", and is only compile tested.
>
> Xen event channels are not internal resources. They still have one end in a
> domain, and are created at the request of privileged domains. This logic
> which "successfully" creates a Xen event channel opens up undesirable failure
> cases with ill-specified XSM policies.
>
> If a domain is permitted to create ioreq servers or memevent listeners, but
> not to create event channels, the ioreq/memevent creation will succeed but
> attempting to bind the returned event channel will fail without any indication
> of a permission error.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Daniel De Graaf <dgdegra@tycho.nsa.gov>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Tim Deegan <tim@xen.org>
> CC: Ian Campbell <Ian.Campbell@citrix.com>
> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> ---
> xen/common/event_channel.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
> index cfe4978..89a7d99 100644
> --- a/xen/common/event_channel.c
> +++ b/xen/common/event_channel.c
> @@ -1160,11 +1160,13 @@ int alloc_unbound_xen_event_channel(
> chn = evtchn_from_port(d, port);
>
> rc = xsm_evtchn_unbound(XSM_TARGET, d, chn, remote_domid);
> + if ( rc )
> + goto out;
out here appears to return port, not rc so you aren't returning failure,
but an even more half setup port than before.
And I think you need to free the port on failure too.
>
> chn->state = ECS_UNBOUND;
> chn->xen_consumer = get_xen_consumer(notification_fn);
> chn->notify_vcpu_id = local_vcpu->vcpu_id;
> - chn->u.unbound.remote_domid = !rc ? remote_domid : DOMID_INVALID;
> + chn->u.unbound.remote_domid = remote_domid;
>
> out:
> spin_unlock(&d->event_lock);
next prev parent reply other threads:[~2015-01-12 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 10:03 [PATCH] RFC XSM/evtchn: Never pretend to have successfully created a Xen event channel Andrew Cooper
2015-01-12 10:22 ` Ian Campbell [this message]
2015-01-12 10:35 ` Andrew Cooper
2015-01-12 22:12 ` Daniel De Graaf
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=1421058132.26317.16.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.