From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Keir Fraser <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2] domctl: fix IRQ permission granting/revocation
Date: Fri, 12 Dec 2014 10:49:30 +0000 [thread overview]
Message-ID: <548AC83A.6020802@citrix.com> (raw)
In-Reply-To: <548AD05D020000780004F329@mail.emea.novell.com>
On 12/12/14 10:24, Jan Beulich wrote:
> Commit 545607eb3c ("x86: fix various issues with handling guest IRQs")
> wasn't really consistent in one respect: The granting of access to an
> IRQ shouldn't assume the pIRQ->IRQ translation to be the same in both
> domains. In fact it is wrong to assume that a translation is already/
> still in place at the time access is being granted/revoked.
>
> What is wanted is to translate the incoming pIRQ to an IRQ for
> the invoking domain (as the pIRQ is the only notion the invoking
> domain has of the IRQ), and grant the subject domain access to
> the resulting IRQ.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Should domain_pirq_to_irq() be using 0 as its default invalid value,
rather than -1? irq 0 is a real irq and could plausibly be wanted to be
passed through to a guest.
~Andrew
> ---
> v2: Also fix initial range check to use current->domain, adjust code
> structure, and extend description (all requested by Ian). Along
> the lines of the first mentioned change, also pass the Xen IRQ
> number to the XSM hook (confirmed okay by Daniel).
> Note that I would hope for this to make unnecessary Stefano's proposed
> tools side change
> http://lists.xenproject.org/archives/html/xen-devel/2014-12/msg00160.html.
>
> --- a/xen/common/domctl.c
> +++ b/xen/common/domctl.c
> @@ -982,18 +982,21 @@ long do_domctl(XEN_GUEST_HANDLE_PARAM(xe
>
> case XEN_DOMCTL_irq_permission:
> {
> - unsigned int pirq = op->u.irq_permission.pirq;
> + unsigned int pirq = op->u.irq_permission.pirq, irq;
> int allow = op->u.irq_permission.allow_access;
>
> - if ( pirq >= d->nr_pirqs )
> + if ( pirq >= current->domain->nr_pirqs )
> + {
> ret = -EINVAL;
> - else if ( !pirq_access_permitted(current->domain, pirq) ||
> - xsm_irq_permission(XSM_HOOK, d, pirq, allow) )
> + break;
> + }
> + irq = pirq_access_permitted(current->domain, pirq);
> + if ( !irq || xsm_irq_permission(XSM_HOOK, d, irq, allow) )
> ret = -EPERM;
> else if ( allow )
> - ret = pirq_permit_access(d, pirq);
> + ret = irq_permit_access(d, irq);
> else
> - ret = pirq_deny_access(d, pirq);
> + ret = irq_deny_access(d, irq);
> }
> break;
>
> --- a/xen/include/xen/iocap.h
> +++ b/xen/include/xen/iocap.h
> @@ -28,22 +28,11 @@
> #define irq_access_permitted(d, i) \
> rangeset_contains_singleton((d)->irq_caps, i)
>
> -#define pirq_permit_access(d, i) ({ \
> - struct domain *d__ = (d); \
> - int i__ = domain_pirq_to_irq(d__, i); \
> - i__ > 0 ? rangeset_add_singleton(d__->irq_caps, i__)\
> - : -EINVAL; \
> -})
> -#define pirq_deny_access(d, i) ({ \
> - struct domain *d__ = (d); \
> - int i__ = domain_pirq_to_irq(d__, i); \
> - i__ > 0 ? rangeset_remove_singleton(d__->irq_caps, i__)\
> - : -EINVAL; \
> -})
> #define pirq_access_permitted(d, i) ({ \
> struct domain *d__ = (d); \
> - rangeset_contains_singleton(d__->irq_caps, \
> - domain_pirq_to_irq(d__, i));\
> + int irq__ = domain_pirq_to_irq(d__, i); \
> + irq__ > 0 && irq_access_permitted(d__, irq__) \
> + ? irq__ : 0; \
> })
>
> #endif /* __XEN_IOCAP_H__ */
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-12-12 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:24 [PATCH v2] domctl: fix IRQ permission granting/revocation Jan Beulich
2014-12-12 10:49 ` Andrew Cooper [this message]
2014-12-12 11:03 ` Jan Beulich
2014-12-12 11:25 ` Ian Campbell
2014-12-12 16:34 ` Ian Campbell
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=548AC83A.6020802@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@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.