From: Kevin Wolf <kwolf@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 3/4] net: split hostname and service by last colon
Date: Fri, 02 Mar 2012 11:35:46 +0100 [thread overview]
Message-ID: <4F50A282.7060401@redhat.com> (raw)
In-Reply-To: <4F5099BC.5050009@redhat.com>
Am 02.03.2012 10:58, schrieb Amos Kong:
> On 02/03/12 11:38, Amos Kong wrote:
>>>> --- a/net.c
>>>> +++ b/net.c
>>>> @@ -84,7 +84,7 @@ static int get_str_sep(char *buf, int buf_size,
>>>> const char **pp, int sep)
>>>> const char *p, *p1;
>>>> int len;
>>>> p = *pp;
>>>> - p1 = strchr(p, sep);
>>>> + p1 = strrchr(p, sep);
>>>> if (!p1)
>>>> return -1;
>>>> len = p1 - p;
>>>
>>> And what if the port isn't specified? I think you would erroneously
>>> interpret the last part of the IP address as port.
>
> Hi Kevin, port must be specified in '-incoming' parameters and migrate
> monitor cmd.
>
> qemu-kvm ... -incoming tcp:$host:$port
> (qemu) migrate -d tcp:$host:$port
>
>
> If use boot up guest by wrong cmdline, qemu will report an error msg.
>
> # ./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -boot n -incoming
> tcp:2312::8272 -monitor stdio
> qemu-system-x86_64: qemu: getaddrinfo: Name or service not known
> tcp_server_start: Invalid argument
> Migration failed. Exit code tcp:2312::8272(-22), exiting.
Which is because 2312: isn't a valid IP address, right? But what if you
have something like 2312::1234:8272? If you misinterpret the 8272 as a
port number, the remaining address is still a valid IPv6 address.
> parse_host_port() are used in four functions in net/socket.c:
> tcp_start_outgoing_migration()
> tcp_start_incoming_migration()
> net_socket_mcast_init()
> net_socket_udp_init()
>
> The argument type of parse_host_port() needs to be changed
> if we replace inet_aton/gethostbyname by getaddrinfo.
>
> So I will not change parse_host_port(), and verify Ipv6 addr
> in tcp_start_common without parse_host_port.
Why not change the prototype of parse_host_port() and modify all callers?
Kevin
next prev parent reply other threads:[~2012-03-02 10:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 6:26 [PATCH 0/4] support to migrate with IPv6 address Amos Kong
2012-02-10 6:26 ` [Qemu-devel] " Amos Kong
2012-02-10 6:27 ` [PATCH 1/4] Use getaddrinfo for migration Amos Kong
2012-02-10 6:27 ` [Qemu-devel] " Amos Kong
2012-02-24 9:08 ` Kevin Wolf
2012-03-02 3:33 ` Amos Kong
2012-03-02 3:33 ` [Qemu-devel] " Amos Kong
2012-03-02 10:28 ` Kevin Wolf
2012-02-24 9:34 ` Kevin Wolf
2012-03-02 2:50 ` Amos Kong
2012-03-02 2:50 ` [Qemu-devel] " Amos Kong
2012-03-02 10:21 ` Kevin Wolf
2012-03-02 10:21 ` [Qemu-devel] " Kevin Wolf
2012-03-02 10:25 ` Michael Tokarev
2012-03-02 10:25 ` [Qemu-devel] " Michael Tokarev
2012-03-02 10:41 ` Daniel P. Berrange
2012-03-02 10:41 ` Daniel P. Berrange
2012-03-05 8:03 ` Amos Kong
2012-03-05 8:03 ` Amos Kong
2012-02-10 6:27 ` [PATCH 2/4] net/socket: allow ipv6 for net_socket_listen_init and socket_connect_init Amos Kong
2012-02-10 6:27 ` [Qemu-devel] " Amos Kong
2012-02-24 9:25 ` Kevin Wolf
2012-02-10 6:27 ` [PATCH 3/4] net: split hostname and service by last colon Amos Kong
2012-02-10 6:27 ` [Qemu-devel] " Amos Kong
2012-02-24 9:29 ` Kevin Wolf
2012-03-02 3:38 ` Amos Kong
2012-03-02 9:58 ` Amos Kong
2012-03-02 10:35 ` Kevin Wolf [this message]
2012-03-02 19:54 ` Laine Stump
2012-03-02 19:54 ` Laine Stump
2012-03-05 8:57 ` Kevin Wolf
2012-03-05 8:57 ` Kevin Wolf
2012-03-05 8:59 ` Amos Kong
2012-03-05 9:06 ` Kevin Wolf
2012-02-10 6:27 ` [PATCH 4/4] net: support to include ipv6 address by brackets Amos Kong
2012-02-10 6:27 ` [Qemu-devel] " Amos Kong
2012-02-24 9:40 ` [Qemu-devel] [PATCH 0/4] support to migrate with IPv6 address Kevin Wolf
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=4F50A282.7060401@redhat.com \
--to=kwolf@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 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.