xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>, Wei Liu <wl@xen.org>
Subject: Re: [Xen-devel] [RFC PATCH 4/5] tools: add xenfs tool
Date: Wed, 11 Sep 2019 11:57:26 +0200	[thread overview]
Message-ID: <4ffa80f0-5d63-9d84-9030-9c5eaecc1541@suse.com> (raw)
In-Reply-To: <97a771af-32a3-596d-30e2-7042374d14e3@suse.com>

On 11.09.19 11:30, Jan Beulich wrote:
> On 11.09.2019 08:20, Juergen Gross wrote:
>> --- a/tools/misc/Makefile
>> +++ b/tools/misc/Makefile
>> @@ -24,6 +24,7 @@ INSTALL_SBIN-$(CONFIG_X86)     += xen-lowmemd
>>   INSTALL_SBIN-$(CONFIG_X86)     += xen-mfndump
>>   INSTALL_SBIN-$(CONFIG_X86)     += xen-ucode
>>   INSTALL_SBIN                   += xencov
>> +INSTALL_SBIN                   += xenfs
> 
> Why SBIN? Is there anything wrong with allowing unprivileged
> users r/o access? Or is this because in order to access the
> hypercall interface one needs to be root? If so, we may want
> to consider relaxing/avoiding/bypassing this in some sensible
> way.

Installing to bin is fine with me, but relaxing the root restriction
might be more difficult and/or questionable.

I was thinking of "mounting" the xen-sysfs to either Xenstore or
the kernel's sysfs (probably the latter, as Xenstore in a stubdom
would need to enable access to xen-sysfs for that stubdom ,too).

This would then enable accessing some or all entries from non-root.


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-09-11  9:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  6:19 [Xen-devel] [RFC PATCH 0/5] Add hypervisor sysfs-like support Juergen Gross
2019-09-11  6:19 ` [Xen-devel] [RFC PATCH 1/5] docs: add feature document for Xen " Juergen Gross
2019-09-11  9:28   ` Jan Beulich
2019-09-11  9:29     ` Juergen Gross
2019-09-11  6:19 ` [Xen-devel] [RFC PATCH 2/5] xen: add basic hypervisor filesystem support Juergen Gross
2019-09-11  6:19 ` [Xen-devel] [RFC PATCH 3/5] libs: add libxenfs Juergen Gross
2019-09-11  6:20 ` [Xen-devel] [RFC PATCH 4/5] tools: add xenfs tool Juergen Gross
2019-09-11  9:30   ` Jan Beulich
2019-09-11  9:57     ` Juergen Gross [this message]
2019-09-11 10:07       ` Jan Beulich
2019-09-11 11:34         ` Juergen Gross
2019-09-11 11:50           ` Jan Beulich
2019-09-11 12:41             ` Juergen Gross
2019-09-11  6:20 ` [Xen-devel] [RFC PATCH 5/5] xen: add /buildinfo/config entry to hypervisor filesystem Juergen Gross
2019-09-11  9:24 ` [Xen-devel] [RFC PATCH 0/5] Add hypervisor sysfs-like support Jan Beulich
2019-09-11 10:02   ` Juergen Gross
2019-09-11 11:17 ` Andrew Cooper
2019-09-11 11:29   ` Juergen Gross
2019-09-11 11:54     ` Jan Beulich
2019-09-11 13:01       ` Juergen Gross
2019-09-11 15:01         ` Jan Beulich
2019-09-11 15:06           ` Juergen Gross
2019-09-11 15:20             ` Jan Beulich
2019-09-11 15:26               ` Juergen Gross

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=4ffa80f0-5d63-9d84-9030-9c5eaecc1541@suse.com \
    --to=jgross@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=wl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).