From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v1 2/2] selftests: mptcp: sockopt: add TCP_MAXSEG sockopt tests
Date: Wed, 23 Apr 2025 17:46:16 +0800 [thread overview]
Message-ID: <996f8df8fbbace706d3972f5d3a7727c2e652239.camel@kernel.org> (raw)
In-Reply-To: <1d68fc7d-06e7-493c-a207-658035c37af9@kernel.org>
Hi Matt,
Thanks for the review.
> Hi Geliang,
>
> On 22/04/2025 11:30, Geliang Tang wrote:
> > From: Geliang Tang <tanggeliang@kylinos.cn>
> >
> > This patch adds the TCP_MAXSEG sockopt tests in mptcp_sockopt.c.
> > Since
> > in getsockopt TCP_MAXSEG, the "user_mss" value can be obtained only
> > in
> > the LISTEN state (see do_tcp_getsockopt in net/ipv4/tcp.c), the
> > test
> > items are added to server() instead of client().
>
> I think it is better to use packetdrill to do such validation,
> similar
> to what was done with other socket options. No?
>
> > Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> > ---
> > .../selftests/net/mptcp/mptcp_sockopt.c | 22
> > +++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> >
> > diff --git a/tools/testing/selftests/net/mptcp/mptcp_sockopt.c
> > b/tools/testing/selftests/net/mptcp/mptcp_sockopt.c
> > index 926b0be87c99..e2043c0261bd 100644
> > --- a/tools/testing/selftests/net/mptcp/mptcp_sockopt.c
> > +++ b/tools/testing/selftests/net/mptcp/mptcp_sockopt.c
> > @@ -689,6 +689,26 @@ static int xaccept(int s)
> > return fd;
> > }
> >
> > +static void test_tcp_maxseg_sockopt(int fd)
> > +{
> > + int maxseg = 1000;
> > + socklen_t s;
> > + int r;
> > +
> > + s = sizeof(maxseg);
> > + r = setsockopt(fd, IPPROTO_TCP, TCP_MAXSEG, &maxseg, s);
> > + if (r != 0)
> > + die_perror("setsockopt TCP_MAXSEG");
> > +
> > + maxseg = 0;
> > + r = getsockopt(fd, IPPROTO_TCP, TCP_MAXSEG, &maxseg, &s);
> > + if (r != -1 && errno != EINVAL)
> > + die_perror("getsockopt TCP_MAXSEG did not indicate
> > -EINVAL");
> > +
> > + if (maxseg != 1000)
> > + xerror("maxseg=%d", maxseg);
> > +}
>
> Here, you set and get the value, but you don't really check the
> behaviour is the one we expect.
>
> It is important to check the behaviour. It would be easier to do that
> with packetdrill I think.
I totally agree, but I want to verify the set and get values in this
set first, I will add packetdrill tests for it later (once I learn how
to modify packetdrill).
Thanks,
-Geliang
>
> > +
> > static int server(int pipefd)
> > {
> > int fd = -1, r;
> > @@ -713,6 +733,8 @@ static int server(int pipefd)
> >
> > process_one_client(r, pipefd);
> >
> > + test_tcp_maxseg_sockopt(fd);
> > +
> > return 0;
> > }
> >
>
> Cheers,
> Matt
next prev parent reply other threads:[~2025-04-23 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 9:30 [PATCH mptcp-next v1 0/2] Add TCP_MAXSEG socket option support Geliang Tang
2025-04-22 9:30 ` [PATCH mptcp-next v1 1/2] mptcp: add TCP_MAXSEG sockopt support Geliang Tang
2025-04-22 11:18 ` Matthieu Baerts
2025-04-22 9:30 ` [PATCH mptcp-next v1 2/2] selftests: mptcp: sockopt: add TCP_MAXSEG sockopt tests Geliang Tang
2025-04-22 11:20 ` Matthieu Baerts
2025-04-23 9:46 ` Geliang Tang [this message]
2025-04-22 10:52 ` [PATCH mptcp-next v1 0/2] Add TCP_MAXSEG socket option support MPTCP CI
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=996f8df8fbbace706d3972f5d3a7727c2e652239.camel@kernel.org \
--to=geliang@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@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