All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@cloudius-systems.com>
To: Stefan Hajnoczi <stefanha@gmail.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 16:39:34 +0200	[thread overview]
Message-ID: <5284E0A6.30402@cloudius-systems.com> (raw)
In-Reply-To: <20131114132940.GB26847@stefanha-thinkpad.redhat.com>

On 11/14/2013 03:29 PM, Stefan Hajnoczi wrote:
> 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.

And it was, indeed, broken.

>
>> 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.

Or maybe installed without the capabilities?  This way if the user 
invokes qemu with sudo, it still works as before.

      reply	other threads:[~2013-11-14 14:39 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
2013-11-14 14:39   ` Avi Kivity [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=5284E0A6.30402@cloudius-systems.com \
    --to=avi@cloudius-systems.com \
    --cc=crobinso@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.