From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 3/9] sockets: pull code for testing IP availability out of specific test
Date: Mon, 12 Mar 2018 19:18:24 +0000 [thread overview]
Message-ID: <20180312191824.GA15677@redhat.com> (raw)
In-Reply-To: <8ed40a69-95a9-c259-d21e-eb239b950754@redhat.com>
On Mon, Mar 12, 2018 at 01:08:44PM -0500, Eric Blake wrote:
> On 03/12/2018 12:46 PM, Daniel P. Berrangé wrote:
> > On Mon, Mar 12, 2018 at 12:49:33PM +0000, Daniel P. Berrangé wrote:
> > > From: "Daniel P. Berrange" <berrange@redhat.com>
> > >
> > > The test-io-channel-socket.c file has some useful helper functions for
> > > checking if a specific IP protocol is available. Other tests need to
> > > perform similar kinds of checks to avoid running tests that will fail
> > > due to missing IP protocols.
> > >
> > > Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> > > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > > ---
>
> > > + if (socket_can_bind("::1") < 0) {
> > > + if (errno != EADDRNOTAVAIL) {
> > > + return -1;
> > > + }
> > > + } else {
> > > + *has_ipv6 = true;
> > > + }
> > > +
> >
> > Sigh, I should have kept the new code identical to the old code,
> > rather than trying to improve it, as this is in fact broken. The
> > socket_can_bind() is mistakenly returning '0' when EADDRNOTAVAIL
> > is set, so we always set the has_ipv4|6 vars to true.
> >
> > It needs this squashed in:
>
> The squash makes sense; with that, you can keep the R-b I added on the
> series (I guess that shows I only read the code, not tried to run the
> testsuite with the code applied, or I might have found this too).
Even if you had run the testsuite (like I did), you would not have seen
the bug unless your host has IPv6 disabled *entirely*. Fortunately
Travis hits that scenario which is how I noticed when I sent my branch
through Travis prior to generating a pull request :-)
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-03-12 19:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 12:49 [Qemu-devel] [PATCH v5 0/9] Enable passing pre-opened chardev socket FD Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 1/9] char: don't silently skip tn3270 protocol init when TLS is enabled Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 2/9] cutils: add qemu_strtoi & qemu_strtoui parsers for int/unsigned int types Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 3/9] sockets: pull code for testing IP availability out of specific test Daniel P. Berrangé
2018-03-12 17:46 ` Daniel P. Berrangé
2018-03-12 18:08 ` Eric Blake
2018-03-12 19:18 ` Daniel P. Berrangé [this message]
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 4/9] sockets: strengthen test suite IP protocol availability checks Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 5/9] sockets: move fd_is_socket() into common sockets code Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 6/9] sockets: check that the named file descriptor is a socket Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 7/9] sockets: allow SocketAddress 'fd' to reference numeric file descriptors Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 8/9] char: refactor parsing of socket address information Daniel P. Berrangé
2018-03-12 12:49 ` [Qemu-devel] [PATCH v5 9/9] char: allow passing pre-opened socket file descriptor at startup Daniel P. Berrangé
2018-03-12 13:12 ` [Qemu-devel] [PATCH v5 0/9] Enable passing pre-opened chardev socket FD Eric Blake
2018-03-12 13:14 ` Daniel P. Berrangé
2018-03-12 14:01 ` Eric Blake
2018-03-12 14:41 ` Eric Blake
2018-03-12 17:57 ` no-reply
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=20180312191824.GA15677@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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 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.