diff options
author | Daniel P. Berrange | 2017-05-17 19:35:40 +0200 |
---|---|---|
committer | Daniel P. Berrange | 2017-07-14 15:28:29 +0200 |
commit | 4dc5d815c43b0138e5d6753e788343f6e2cb6b5f (patch) | |
tree | 38a7df99d9629f4a0b68b7a7a6a1fb6369561e95 /hw/s390x/css-bridge.c | |
parent | sockets: ensure we can bind to both ipv4 & ipv6 separately (diff) | |
download | qemu-4dc5d815c43b0138e5d6753e788343f6e2cb6b5f.tar.gz qemu-4dc5d815c43b0138e5d6753e788343f6e2cb6b5f.tar.xz qemu-4dc5d815c43b0138e5d6753e788343f6e2cb6b5f.zip |
sockets: don't block IPv4 clients when listening on "::"
When inet_parse() parses the hostname, it is forcing the
has_ipv6 && ipv6 flags if the address contains a ":". This
means that if the user had set the ipv4=on flag, to try to
restrict the listener to just ipv4, an error would not have
been raised. eg
-incoming tcp:[::]:9000,ipv4
should have raised an error because listening for IPv4
on "::" is a non-sensical combination. With this removed,
we now call getaddrinfo() on "::" passing PF_INET and
so getaddrinfo reports an error about the hostname being
incompatible with the requested protocol:
qemu-system-x86_64: -incoming tcp:[::]:9000,ipv4: address resolution
failed for :::9000: Address family for hostname not supported
Likewise it is explicitly setting the has_ipv4 & ipv4
flags when the address contains only digits + '.'. This
has no ill-effect, but also has no benefit, so is removed.
Acked-by: Gerd Hoffmann <kraxel@gmail.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'hw/s390x/css-bridge.c')
0 files changed, 0 insertions, 0 deletions