From: Luiz Capitulino <lcapitulino@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
stefanha@linux.vnet.ibm.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] net: tap-linux: Fix unhelpful error message
Date: Thu, 27 Oct 2011 16:51:39 -0200 [thread overview]
Message-ID: <20111027165139.5d5e4cfd@doriath> (raw)
In-Reply-To: <20111014150510.610f6deb@doriath>
On Fri, 14 Oct 2011 15:05:10 -0300
Luiz Capitulino <lcapitulino@redhat.com> wrote:
> I'm getting:
>
> could not configure /dev/net/tun (tap%d): Operation not permitted
>
> When the ioctl() fails, ifr.ifr_name will most likely not be overwritten.
> So we better only use it when ifname contains a string.
I had forgotten about this one, but just got it again... Stefan, I think
this is a candidate for the trivial tree.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
>
> PS: Trivial tree candidate.
>
> net/tap-linux.c | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/net/tap-linux.c b/net/tap-linux.c
> index ff8cad0..41d581b 100644
> --- a/net/tap-linux.c
> +++ b/net/tap-linux.c
> @@ -73,7 +73,11 @@ int tap_open(char *ifname, int ifname_size, int *vnet_hdr, int vnet_hdr_required
> pstrcpy(ifr.ifr_name, IFNAMSIZ, "tap%d");
> ret = ioctl(fd, TUNSETIFF, (void *) &ifr);
> if (ret != 0) {
> - error_report("could not configure %s (%s): %m", PATH_NET_TUN, ifr.ifr_name);
> + if (ifname[0] != '\0') {
> + error_report("could not configure %s (%s): %m", PATH_NET_TUN, ifr.ifr_name);
> + } else {
> + error_report("could not configure %s: %m", PATH_NET_TUN);
> + }
> close(fd);
> return -1;
> }
next prev parent reply other threads:[~2011-10-27 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 18:05 [Qemu-devel] [PATCH] net: tap-linux: Fix unhelpful error message Luiz Capitulino
2011-10-27 18:51 ` Luiz Capitulino [this message]
2011-10-28 7:40 ` Stefan Hajnoczi
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=20111027165139.5d5e4cfd@doriath \
--to=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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).