From: Stefan Hajnoczi <stefanha@gmail.com>
To: Avi Kivity <avi@cloudius-systems.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] build: set up capabilities on qemu-bridge-helper
Date: Thu, 14 Nov 2013 14:29:40 +0100 [thread overview]
Message-ID: <20131114132940.GB26847@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <c66f8b4405fbe3d1ad36d85392bbc556c7959774.1384254624.git.avi@cloudius-systems.com>
On Tue, Nov 12, 2013 at 01:10:24PM +0200, Avi Kivity wrote:
> Out-of-the-box, 'make install' sets up an unusable qemu-bridge-helper since
> it doesn't have the required capabilities.
>
> Fix by adding them.
Up until now, downstreams had to make the bridge helper executable
setuid, add the cap_net_admin capability, or they did nothing and it was
broken ;-). CCing downstream package maintainers in case they have any
comments on this patch.
> Note: this may break installing as non-root. This is actually the right
> thing to do, since not setting up the capability would result in a broken
> setup. Perhaps we need a configure flag to disable helpers.
Users who have been successfully installing QEMU would be upset if it
suddenly starts failing after this patch. The bridge helper is a niche
feature that shouldn't cause a regression for the majority of users who
don't care about it.
If we're installing non-root then the bridge helper simply shouldn't be
installed.
> Signed-off-by: Avi Kivity <avi@cloudius-systems.com>
> ---
> Makefile | 3 +++
> rules.mak | 2 ++
> 2 files changed, 5 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index b15003f..af7748c 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -188,6 +188,7 @@ qemu-img$(EXESUF): qemu-img.o $(block-obj-y) libqemuutil.a libqemustub.a
> qemu-nbd$(EXESUF): qemu-nbd.o $(block-obj-y) libqemuutil.a libqemustub.a
> qemu-io$(EXESUF): qemu-io.o $(block-obj-y) libqemuutil.a libqemustub.a
>
> +qemu-bridge-helper$(EXESUF).capabilities = cap_net_admin
> qemu-bridge-helper$(EXESUF): qemu-bridge-helper.o
>
> fsdev/virtfs-proxy-helper$(EXESUF): fsdev/virtfs-proxy-helper.o fsdev/virtio-9p-marshal.o libqemuutil.a libqemustub.a
> @@ -345,6 +346,8 @@ endif
> ifneq ($(HELPERS-y),)
> $(INSTALL_DIR) "$(DESTDIR)$(libexecdir)"
> $(INSTALL_PROG) $(STRIP_OPT) $(HELPERS-y) "$(DESTDIR)$(libexecdir)"
> + $(SETCAP) $(foreach helper, $(HELPERS-y), \
> + $($(helper).capabilities)+pe "$(DESTDIR)$(libexecdir)"/$(helper))
> endif
> ifneq ($(BLOBS),)
> set -e; for x in $(BLOBS); do \
> diff --git a/rules.mak b/rules.mak
> index 49edb9b..9194c79 100644
> --- a/rules.mak
> +++ b/rules.mak
> @@ -177,3 +177,5 @@ $(shell mkdir -p $(sort $(foreach var,$(nested-vars),$(dir $($(var))))))
> $(foreach var,$(nested-vars), $(eval \
> -include $(addsuffix *.d, $(sort $(dir $($(var)))))))
> endef
> +
> +SETCAP = setcap
> \ No newline at end of file
> --
> 1.8.3.1
>
>
next prev parent reply other threads:[~2013-11-14 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 11:10 [Qemu-devel] [PATCH] build: set up capabilities on qemu-bridge-helper Avi Kivity
2013-11-12 19:23 ` Eric Blake
2013-11-12 19:27 ` Avi Kivity
2013-11-14 13:29 ` Stefan Hajnoczi [this message]
2013-11-14 14:39 ` Avi Kivity
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=20131114132940.GB26847@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=avi@cloudius-systems.com \
--cc=crobinso@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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).