All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: Orit Wasserman <owasserm@redhat.com>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, mdroth@linux.vnet.ibm.com,
	quintela@redhat.com, armbru@redhat.com, mst@redhat.com,
	qemu-devel@nongnu.org, lcapitulino@redhat.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] nonblocking connect address handling cleanup
Date: Wed, 12 Sep 2012 22:16:30 +0800	[thread overview]
Message-ID: <5050993E.6010705@redhat.com> (raw)
In-Reply-To: <1347448378-23915-1-git-send-email-owasserm@redhat.com>

On 12/09/12 19:12, Orit Wasserman wrote:
> getaddrinfo can give us a list of addresses, but we only try to
> connect to the first one. If that fails we never proceed to
> the next one.  This is common on desktop setups that often have ipv6
> configured but not actually working.
> A simple way to reproduce the problem is migration:
> for the destination use -incoming tcp:0:4444, run migrate -d tcp:localhost:4444
> migration will fail on hosts that have both IPv4 and IPV6 address for localhost.
>
> To fix this, refactor address resolution code and make inet_nonblocking_connect
> retry connection with a different address.


Looks good to me.

Reviewed-by: Amos Kong <akong@redhat.com>
Tested-by: Amos Kong <akong@redhat.com>


> Orit Wasserman (3):
>    Refactor inet_connect_opts function
>    Separate inet_connect into inet_connect (blocking) and
>      inet_nonblocking_connect
>    Fix address handling in inet_nonblocking_connect
>
>   migration-tcp.c |   29 ++-----
>   nbd.c           |    2 +-
>   qemu-sockets.c  |  254 +++++++++++++++++++++++++++++++++++++++++--------------
>   qemu_socket.h   |    9 ++-
>   ui/vnc.c        |    2 +-
>   5 files changed, 208 insertions(+), 88 deletions(-)
>

-- 
			Amos.

  parent reply	other threads:[~2012-09-12 14:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 11:12 [Qemu-devel] [PATCH v2 0/3] nonblocking connect address handling cleanup Orit Wasserman
2012-09-12 11:12 ` [Qemu-devel] [PATCH v2 1/3] Refactor inet_connect_opts function Orit Wasserman
2012-09-13 12:35   ` Markus Armbruster
2012-09-13 16:44     ` Orit Wasserman
2012-09-13 16:52     ` Orit Wasserman
2012-09-14  7:37       ` Michael S. Tsirkin
2012-09-13 13:14   ` Markus Armbruster
2012-09-13 16:44     ` Orit Wasserman
2012-09-12 11:12 ` [Qemu-devel] [PATCH v2 2/3] Separate inet_connect into inet_connect (blocking) and inet_nonblocking_connect Orit Wasserman
2012-09-13 12:44   ` Markus Armbruster
2012-09-13 16:40     ` Orit Wasserman
2012-09-12 11:12 ` [Qemu-devel] [PATCH v2 3/3] Fix address handling in inet_nonblocking_connect Orit Wasserman
2012-09-13 13:22   ` Markus Armbruster
2012-09-13 13:32     ` Michael S. Tsirkin
2012-09-13 14:23       ` Orit Wasserman
2012-09-13 17:27     ` Orit Wasserman
2012-09-12 14:16 ` Amos Kong [this message]
2012-09-12 20:37 ` [Qemu-devel] [PATCH v2 0/3] nonblocking connect address handling cleanup Michael S. Tsirkin

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=5050993E.6010705@redhat.com \
    --to=akong@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 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.