From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: mjt@tls.msk.ru, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] give some useful error messages when tap open
Date: Wed, 2 Jun 2010 15:33:12 -0300 [thread overview]
Message-ID: <20100602153312.5f665cb2@redhat.com> (raw)
In-Reply-To: <m3r5kpp9xp.fsf@blackfin.pond.sub.org>
On Wed, 02 Jun 2010 20:26:58 +0200
Markus Armbruster <armbru@redhat.com> wrote:
> Luiz Capitulino <lcapitulino@redhat.com> writes:
>
> > From: Michael Tokarev <mjt@tls.msk.ru>
> >
> > In net/tap-linux.c, when manipulation of /dev/net/tun fails, it prints
> > (with fprintf) something like this:
> >
> > warning: could not open /dev/net/tun: no virtual network emulation
> >
> > this has 2 issues:
> > 1) it is not a warning really, it's a fatal error (kvm exits after
> > that),
> > 2) there's no indication as of what's actually wrong: printing errno there
> > is helpful.
> >
> > The patch below removes the "warning" prefix, uses %m (since it's linux,
> > %m is available as format modifier), and changes fprintf() to %qemu_error().
>
> To error_report(), you mean.
It's the original commit log.. Should this be fixed? If so, Michael,
could you resend?
>
> > Now it prints something like this instead:
> >
> > could not configure /dev/net/tun: Device or resource busy
> >
> > (there are 2 messages like that in the same function)
> >
> > This fixes Debian bug #578154, see
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578154
> >
> > Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
>
> Looks good.
>
next prev parent reply other threads:[~2010-06-02 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 17:33 [Qemu-devel] [PATCH] give some useful error messages when tap open Luiz Capitulino
2010-06-02 18:26 ` Markus Armbruster
2010-06-02 18:33 ` Luiz Capitulino [this message]
2010-06-03 7:07 ` Markus Armbruster
2010-06-23 1:47 ` Anthony Liguori
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=20100602153312.5f665cb2@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@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).