From: Ross Philipson <ross.philipson@citrix.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: XSM dummy policy blocking event channel creation
Date: Fri, 3 May 2013 09:14:36 -0400 [thread overview]
Message-ID: <5183B83C.2090705@citrix.com> (raw)
In-Reply-To: <51828E4B.3060407@tycho.nsa.gov>
On 05/02/2013 12:03 PM, Daniel De Graaf wrote:
> That would work; it looks like it would be easier than pulling the XSM hook
> out of the function. The important part is that the user-accessible caller
> still needs to execute the hook. Other callers bypassing the permission
> check will need similar justification for doing that, but that discussion
> should wait until those additional callers exist.
Thanks for your help. I implemented that and it is working nicely.
--
Ross Philipson
prev parent reply other threads:[~2013-05-03 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:40 XSM dummy policy blocking event channel creation Ross Philipson
2013-05-01 20:50 ` Daniel De Graaf
2013-05-01 21:09 ` Ross Philipson
2013-05-01 22:02 ` Daniel De Graaf
2013-05-02 14:23 ` Ross Philipson
2013-05-02 15:10 ` Daniel De Graaf
2013-05-02 15:37 ` Ross Philipson
2013-05-02 16:03 ` Daniel De Graaf
2013-05-03 13:14 ` Ross Philipson [this message]
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=5183B83C.2090705@citrix.com \
--to=ross.philipson@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--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.