From: Matthieu Baerts <matttbe@kernel.org>
To: Gang Yan <yangang@kylinos.cn>, mptcp@lists.linux.dev
Cc: Geliang Tang <geliang@kernel.org>
Subject: Re: [mptcp-next v2 2/7] selftests: mptcp: refactor send_query parameters for code clarity
Date: Tue, 22 Apr 2025 15:22:50 +0200 [thread overview]
Message-ID: <6f1f5c0f-c7fe-472c-8dd5-87bf34d43c92@kernel.org> (raw)
In-Reply-To: <afbbf4fc074b0d26b4954db0a750cadea1b67a62.1744793332.git.yangang@kylinos.cn>
Hi Gang,
On 16/04/2025 10:59, Gang Yan wrote:
> This patch use 'inet_diag_req_v2' instead of 'token' as parameters of
> send_query, and construct the req in 'get_mptcpinfo'. This modification
> can enhance the enhancing clarity of the code, and prepare for the
> dump_subflow_info.
>
> Co-developed-by: Geliang Tang <geliang@kernel.org>
> Signed-off-by: Geliang Tang <geliang@kernel.org>
> Signed-off-by: Gang Yan <yangang@kylinos.cn>
> ---
> .../testing/selftests/net/mptcp/mptcp_diag.c | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_diag.c b/tools/testing/selftests/net/mptcp/mptcp_diag.c
> index ea7cb1128044..8a5b7745c58c 100644
> --- a/tools/testing/selftests/net/mptcp/mptcp_diag.c
> +++ b/tools/testing/selftests/net/mptcp/mptcp_diag.c
> @@ -62,7 +62,7 @@ static void die_usage(int r)
> exit(r);
> }
>
> -static void send_query(int fd, __u32 token)
> +static void send_query(int fd, struct inet_diag_req_v2 *r)
> {
> struct sockaddr_nl nladdr = {
> .nl_family = AF_NETLINK
> @@ -76,19 +76,13 @@ static void send_query(int fd, __u32 token)
> .nlmsg_type = SOCK_DIAG_BY_FAMILY,
> .nlmsg_flags = NLM_F_REQUEST
> },
> - .r = {
> - .sdiag_family = AF_INET,
> - /* Real proto is set via INET_DIAG_REQ_PROTOCOL */
> - .sdiag_protocol = IPPROTO_TCP,
> - .id.idiag_cookie[0] = token,
> - }
> + .r = *r
> };
> struct rtattr rta_proto;
> struct iovec iov[6];
> int iovlen = 1;
> __u32 proto;
>
> - req.r.idiag_ext |= (1 << (INET_DIAG_INFO - 1));
> proto = IPPROTO_MPTCP;
> rta_proto.rta_type = INET_DIAG_REQ_PROTOCOL;
> rta_proto.rta_len = RTA_LENGTH(sizeof(proto));
> @@ -229,13 +223,20 @@ static void recv_nlmsg(int fd)
>
> static void get_mptcpinfo(__u32 token)
> {
> + struct inet_diag_req_v2 r = {
> + .sdiag_family = AF_INET,
> + /* Real proto is set via INET_DIAG_REQ_PROTOCOL */
> + .sdiag_protocol = IPPROTO_TCP,
> + .id.idiag_cookie[0] = token,
> + };
> int fd;
>
> fd = socket(AF_NETLINK, SOCK_RAW, NETLINK_SOCK_DIAG);
> if (fd < 0)
> die_perror("Netlink socket");
>
> - send_query(fd, token);
> + r.idiag_ext |= (1 << (INET_DIAG_INFO - 1));
Out of curiosity, why can you not set idiag_ext above, when 'r' is declared?
> + send_query(fd, &r);
> recv_nlmsg(fd);
>
> close(fd);
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-04-22 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 8:59 [mptcp-next v2 0/7] Add 'dump_subflow' test in selftests Gang Yan
2025-04-16 8:59 ` [mptcp-next v2 1/7] selftests: mptcp: add struct params in mptcp_diag Gang Yan
2025-04-16 8:59 ` [mptcp-next v2 2/7] selftests: mptcp: refactor send_query parameters for code clarity Gang Yan
2025-04-22 13:22 ` Matthieu Baerts [this message]
2025-04-16 8:59 ` [mptcp-next v2 3/7] selftests: mptcp: refine the 'iovlen' handling logic Gang Yan
2025-04-22 13:22 ` Matthieu Baerts
2025-04-16 8:59 ` [mptcp-next v2 4/7] selftests: mptcp: refactor NLMSG handling with 'proto' Gang Yan
2025-04-16 8:59 ` [mptcp-next v2 5/7] selftests: mptcp: add a helper to get subflow_info Gang Yan
2025-04-22 13:23 ` Matthieu Baerts
2025-04-16 8:59 ` [mptcp-next v2 6/7] selftests: mptcp: add a helper to print subflow_info Gang Yan
2025-04-22 13:23 ` Matthieu Baerts
2025-04-16 8:59 ` [mptcp-next v2 7/7] selftests: mptcp: add chk_sublfow in diag.sh Gang Yan
2025-04-22 13:24 ` Matthieu Baerts
2025-04-16 10:20 ` [mptcp-next v2 0/7] Add 'dump_subflow' test in selftests MPTCP CI
2025-04-22 13:22 ` Matthieu Baerts
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=6f1f5c0f-c7fe-472c-8dd5-87bf34d43c92@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=yangang@kylinos.cn \
/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