From: Orit Wasserman <owasserm@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: aliguori@us.ibm.com, kvm@vger.kernel.org, quintela@redhat.com,
jasowang@redhat.com, qemu-devel@nongnu.org, laine@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 3/9] net: introduce tcp_client_start()
Date: Mon, 05 Mar 2012 15:36:21 +0200 [thread overview]
Message-ID: <4F54C155.4000102@redhat.com> (raw)
In-Reply-To: <20120305100338.3595.19978.stgit@dhcp-8-167.nay.redhat.com>
On 03/05/2012 12:03 PM, Amos Kong wrote:
> Introduce tcp_client_start() by moving original code in
> tcp_start_outgoing_migration().
>
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> net.c | 39 +++++++++++++++++++++++++++++++++++++++
> qemu_socket.h | 1 +
> 2 files changed, 40 insertions(+), 0 deletions(-)
>
> diff --git a/net.c b/net.c
> index 0260968..5c20e22 100644
> --- a/net.c
> +++ b/net.c
> @@ -126,6 +126,45 @@ int tcp_server_start(const char *str, int *fd)
> return ret;
> }
>
> +int tcp_client_start(const char *str, int *fd)
> +{
> + struct sockaddr_in saddr;
> + int ret;
> +
> + if (parse_host_port(&saddr, str) < 0) {
> + return -EINVAL;
You use this in order to know when to call migrate_fd_error this is problematic as another error can return this error code.
I think that setting *fd = -1 in the beginning of the function would be enough.
Orit
> + }
> +
> + *fd = qemu_socket(PF_INET, SOCK_STREAM, 0);
> + if (fd < 0) {
> + perror("socket");
> + return -1;
> + }
> + socket_set_nonblock(*fd);
> +
> + for (;;) {
> + ret = connect(*fd, (struct sockaddr *)&saddr, sizeof(saddr));
> + if (ret < 0) {
> + ret = -socket_error();
> + if (ret == -EINPROGRESS) {
> + break;
> +#ifdef _WIN32
> + } else if (ret == -WSAEALREADY || ret == -WSAEINVAL) {
> + break;
> +#endif
> + } else if (ret != -EINTR && ret != -EWOULDBLOCK) {
> + perror("connect");
> + closesocket(*fd);
> + return -1;
should be return ret;
> + }
> + } else {
> + break;
> + }
> + }
> +
> + return ret;
> +}
> +
> int parse_host_port(struct sockaddr_in *saddr, const char *str)
> {
> char buf[512];
> diff --git a/qemu_socket.h b/qemu_socket.h
> index d612793..9246578 100644
> --- a/qemu_socket.h
> +++ b/qemu_socket.h
> @@ -55,6 +55,7 @@ int unix_connect_opts(QemuOpts *opts);
> int unix_connect(const char *path);
>
> int tcp_server_start(const char *str, int *fd);
> +int tcp_client_start(const char *str, int *fd);
>
> /* Old, ipv4 only bits. Don't use for new code. */
> int parse_host_port(struct sockaddr_in *saddr, const char *str);
>
>
next prev parent reply other threads:[~2012-03-05 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 10:03 [Qemu-devel] [PATCH v2 0/9] support to migrate with IPv6 address Amos Kong
2012-03-05 10:03 ` [Qemu-devel] [PATCH v2 1/9] net: introduce tcp_server_start() Amos Kong
2012-03-05 13:25 ` Orit Wasserman
2012-03-05 13:49 ` Amos Kong
2012-03-05 10:03 ` [Qemu-devel] [PATCH v2 2/9] net: use tcp_server_start() for tcp server creation Amos Kong
2012-03-05 13:27 ` Orit Wasserman
2012-03-05 13:44 ` Amos Kong
2012-03-05 10:03 ` [Qemu-devel] [PATCH v2 3/9] net: introduce tcp_client_start() Amos Kong
2012-03-05 13:26 ` Orit Wasserman
2012-03-05 13:36 ` Orit Wasserman [this message]
2012-03-05 10:03 ` [Qemu-devel] [PATCH v2 4/9] net: use tcp_client_start for tcp client creation Amos Kong
2012-03-05 13:39 ` Orit Wasserman
2012-03-05 10:03 ` [Qemu-devel] [PATCH v2 5/9] net: refector tcp_*_start functions Amos Kong
2012-03-05 10:04 ` [Qemu-devel] [PATCH v2 6/9] net: use getaddrinfo() in tcp_start_common Amos Kong
2012-03-05 10:04 ` [Qemu-devel] [PATCH v2 7/9] net: introduce parse_host_port_info() Amos Kong
2012-03-05 10:04 ` [Qemu-devel] [PATCH v2 8/9] net: split hostname and service by last colon Amos Kong
2012-03-05 10:04 ` [Qemu-devel] [PATCH v2 9/9] net: support to include ipv6 address by brackets Amos Kong
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=4F54C155.4000102@redhat.com \
--to=owasserm@redhat.com \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=laine@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 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).