]> xenbits.xensource.com Git - xen.git/commit
xsm/evtchn: never pretend to have successfully created a Xen event channel
authorAndrew Cooper <andrew.cooper3@citrix.com>
Tue, 3 Feb 2015 14:27:18 +0000 (15:27 +0100)
committerJan Beulich <jbeulich@suse.com>
Tue, 3 Feb 2015 14:27:18 +0000 (15:27 +0100)
commit461a8d3916a77695b4137c6b27e7c434e03035ff
tree4d3ffe7a2fba7cd03d1337582a7c67096fa0d459
parentdd971e41820dc33e1da1c429dfc3c7ee32b4795e
xsm/evtchn: never pretend to have successfully created a Xen event channel

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>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
master commit: 09aa4759faa29c1fe735266de4c79f17329bd67b
master date: 2015-01-20 10:42:26 +0100
xen/common/event_channel.c