From: Geliang Tang <geliang@kernel.org>
To: zhenwei pi <pizhenwei@bytedance.com>,
linux-kernel@vger.kernel.org, mptcp@lists.linux.dev,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org
Cc: matttbe@kernel.org, martineau@kernel.org,
viktor.soderqvist@est.tech, zhenwei pi <zhenwei.pi@linux.dev>
Subject: Re: [PATCH] selftests: mptcp: add comment for getaddrinfo
Date: Tue, 08 Apr 2025 09:43:24 +0800 [thread overview]
Message-ID: <ae367fb7158e2f1c284a4acaea86f96a7a95b0c4.camel@kernel.org> (raw)
In-Reply-To: <20250407085122.1203489-1-pizhenwei@bytedance.com>
Hi zhenwei,
On Mon, 2025-04-07 at 16:51 +0800, zhenwei pi wrote:
> mptcp_connect.c is a startup tutorial of MPTCP programming, however
> there is a lack of ai_protocol(IPPROTO_MPTCP) usage. Add comment for
> getaddrinfo MPTCP support.
>
> Signed-off-by: zhenwei pi <zhenwei.pi@linux.dev>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> tools/testing/selftests/net/mptcp/mptcp_connect.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_connect.c
> b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> index c83a8b47bbdf..6b9031273964 100644
> --- a/tools/testing/selftests/net/mptcp/mptcp_connect.c
> +++ b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> @@ -179,6 +179,18 @@ static void xgetnameinfo(const struct sockaddr
> *addr, socklen_t addrlen,
> }
> }
>
> +/* There is a lack of MPTCP support from glibc, these code leads
> error:
> + * struct addrinfo hints = {
> + * .ai_protocol = IPPROTO_MPTCP,
> + * ...
> + * };
> + * err = getaddrinfo(node, service, &hints, res);
> + * ...
> + * So using IPPROTO_TCP to resolve, and use TCP/MPTCP to create
> socket.
> + *
> + * glibc starts to support MPTCP since v2.42.
> + * Link:
> https://sourceware.org/git/?p=glibc.git;a=commit;h=a8e9022e0f82
Thanks for adding getaddrinfo mptcp support to glibc. I think we should
not only add a comment for getaddrinfo mptcp here, but also add an
example of using it in mptcp_connect.c. I will work with you to
implement this example in v2.
Thanks,
-Geliang
> + */
> static void xgetaddrinfo(const char *node, const char *service,
> const struct addrinfo *hints,
> struct addrinfo **res)
next prev parent reply other threads:[~2025-04-08 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 8:51 zhenwei pi
2025-04-08 1:43 ` Geliang Tang [this message]
2025-04-08 3:09 ` zhenwei pi
2025-04-08 10:57 ` Paolo Abeni
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=ae367fb7158e2f1c284a4acaea86f96a7a95b0c4.camel@kernel.org \
--to=geliang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pizhenwei@bytedance.com \
--cc=viktor.soderqvist@est.tech \
--cc=zhenwei.pi@linux.dev \
/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
all inboxes | Powered by JetHome®