All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zeffertt <alex.zeffertt@eu.citrix.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: [PATCH 1/3] [linux-2.6.18-xen.hg] allow dom0 to use /proc/xen/xenbus for all commands (in add'n to unix domain socket)
Date: Mon, 23 Mar 2009 15:20:01 +0000	[thread overview]
Message-ID: <49C7A8A1.1000106@eu.citrix.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: xenbus_whitelist_commands --]
[-- Type: text/plain, Size: 895 bytes --]

You should be able to run any xenbus command over /proc/xen/xenbus.
Access control should be done in the daemon, not here.
This patch is needed for the libxs fallback to /proc/xen/xenbus to work
for all tools. See xen patch libxc_fallback_domain_open.

Signed-off-by: Diego Ongaro <diego.ongaro@citrix.com>
Signed-off-by: Alex Zeffertt <alex.zeffertt@eu.citrix.com>
---
diff -r 23608d139723 drivers/xen/xenbus/xenbus_dev.c
--- a/drivers/xen/xenbus/xenbus_dev.c	Fri Jul 11 16:08:33 2008 +0100
+++ b/drivers/xen/xenbus/xenbus_dev.c	Fri Jul 11 16:32:29 2008 +0100
@@ -235,6 +235,13 @@
 	case XS_MKDIR:
 	case XS_RM:
 	case XS_SET_PERMS:
+	case XS_DEBUG:
+	case XS_INTRODUCE:
+	case XS_WATCH_EVENT:
+	case XS_ERROR:
+	case XS_IS_DOMAIN_INTRODUCED:
+	case XS_RESUME:
+	case XS_SET_TARGET:
 		if (msg_type == XS_TRANSACTION_START) {
 			trans = kmalloc(sizeof(*trans), GFP_KERNEL);
 			if (!trans) {


[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2009-03-23 15:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=49C7A8A1.1000106@eu.citrix.com \
    --to=alex.zeffertt@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.