From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] Fix handling of IPv4/IPv6 dual stack
Date: Tue, 06 Jun 2017 12:32:46 +0200 [thread overview]
Message-ID: <1496745166.15129.11.camel@redhat.com> (raw)
In-Reply-To: <20170601082935.19993-1-berrange@redhat.com>
On Thu, 2017-06-01 at 09:29 +0100, Daniel P. Berrange wrote:
> This series aims to fix a lot of bugs related to handling of IPv4 /
> IPv6
> dual stack.
>
> - The VNC server mistakenly listened on two separate ports 5900+5901
> when the to= parameter was given
> - IPv6 sockets are accepting IPv4 clients even when IPv4 is set to
> be disabled
> - IPv6 sockets are failing to accept IPv4 clients when IPv4 is not
> set
> to be disabled
> - The VNC server was loosing the ipv4=/ipv6= settings due to a bug
> in the DNS resolver
>
> The behaviour of all this is really subtle and hard to get working
> correctly
> across all the different network backends. Thus, the most important
> part of
> this patch series is the last patch which adds a test case covering
> the
> backends for -vnc, -chardev tcp, -net socket, and -incoming socket,
> with
> a 120 entry matrix.
Acked-by: Gerd Hoffmann <kraxel@gmail.com>
next prev parent reply other threads:[~2017-06-06 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 8:29 [Qemu-devel] [PATCH v3 0/5] Fix handling of IPv4/IPv6 dual stack Daniel P. Berrange
2017-06-01 8:29 ` [Qemu-devel] [PATCH v3 1/5] sockets: ensure we can bind to both ipv4 & ipv6 separately Daniel P. Berrange
2017-06-01 8:29 ` [Qemu-devel] [PATCH v3 2/5] sockets: don't block IPv4 clients when listening on "::" Daniel P. Berrange
2017-06-01 8:29 ` [Qemu-devel] [PATCH v3 3/5] sockets: ensure we don't accept IPv4 clients when IPv4 is disabled Daniel P. Berrange
2017-06-02 4:45 ` Philippe Mathieu-Daudé
2017-06-01 8:29 ` [Qemu-devel] [PATCH v3 4/5] io: preserve ipv4/ipv6 flags when resolving InetSocketAddress Daniel P. Berrange
2017-06-01 8:29 ` [Qemu-devel] [PATCH v3 5/5] tests: add functional test validating ipv4/ipv6 address flag handling Daniel P. Berrange
2017-06-06 10:32 ` Gerd Hoffmann [this message]
2017-06-10 16:06 ` [Qemu-devel] [PATCH v3 0/5] Fix handling of IPv4/IPv6 dual stack Vlad Yasevich
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=1496745166.15129.11.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--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 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).