From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Shaun Reitan <shaun.reitan@ndchost.com>
Cc: Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add ability to provide ifname when using netdev bridge or tap helper
Date: Wed, 17 Jan 2018 11:39:06 +0100 [thread overview]
Message-ID: <39294893-a458-9f40-dc9c-bcac14d8be5e@redhat.com> (raw)
In-Reply-To: <20180117103148.GE19227@redhat.com>
On 17/01/2018 11:31, Daniel P. Berrange wrote:
>
> eg consider the user asks for a tap device called eth1. To the
> sysadmin the user's tap device now looks like a physical NIC.
> This can be even worse if the host does physical NIC hotplug,
> or uses SRIOV. eg consider the host as eth0 -> eth7 for SRIOV
> NICs, and eth3 is given to a guest. Now a user uses the setuid
> helper to ask for a TAP called eth3. When the SRIOV device is
> later released by the guest it will end up called eth8, as the
> TAP device occupies eth3. In bad cases this could even cause
> the host mgmt layer to configure bogus addresses on the eth3
> TAP device instead of the SRIOV device.
>
> If we want to allow ifname to be set via the setuid helper, then IMHO,
> the config file for the helper *must* whitelist the various permitted
> naming patterns.
Indeed, a similar patch has been proposed several times, and always the
response was the same as Daniel's. :)
Paolo
next prev parent reply other threads:[~2018-01-17 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 23:18 [Qemu-devel] [PATCH] Add ability to provide ifname when using netdev bridge or tap helper Shaun Reitan
2018-01-17 3:35 ` Jason Wang
2018-01-17 10:31 ` Daniel P. Berrange
2018-01-17 10:39 ` Paolo Bonzini [this message]
2018-01-17 13:28 ` Philippe Mathieu-Daudé
2018-01-17 10:53 ` Jason Wang
2018-01-17 10:58 ` Daniel P. Berrange
2018-01-17 15:26 ` Eric Blake
2018-01-17 18:11 ` Shaun Reitan
2018-01-18 11:53 ` Jason Wang
2018-01-18 21:56 ` Shaun Reitan
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=39294893-a458-9f40-dc9c-bcac14d8be5e@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shaun.reitan@ndchost.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 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).