mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v4 3/3] selftests: mptcp: update and extend fastclose test-cases
Date: Fri, 9 Sep 2022 17:39:38 +0200	[thread overview]
Message-ID: <8b87693f-66a7-67ce-752e-d98df7162552@tessares.net> (raw)
In-Reply-To: <ccf2c2fc0f7fdca9742c51b3fdc6bb6c5fabec5f.1662713367.git.pabeni@redhat.com>

Hi Paolo,

On 09/09/2022 10:49, Paolo Abeni wrote:
> After the previous patches, the MPTCP protocol can generate
> fast-closes on both ends of the connection. Rework the relevant
> test-case to carefully trigger the fast-close code-path on a
> single end at the time, while ensuring than a predictable amount
> of data is spooled on both ends.
> 
> Additionally add another test-cases for the passive socket
> fast-close.

Thank you for the v4!

The whole series looks good to me.

Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>


I wanted to apply it but I just realised that like with the previous
version Patchew didn't apply this v4 as well. Maybe because there is no
cover-letter?

I just applied these patches manually and I will wait for the CI to send
its report before applying them.

https://github.com/multipath-tcp/mptcp_net-next/commits/patchew/904c47ce96fa8d6d4c961a2480bf3aea702c3a9c.1662713367.git.pabeni@redhat.com

(...)

> diff --git a/tools/testing/selftests/net/mptcp/mptcp_connect.c b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> index 24d4e9cb617e..7e4ce3caa5ed 100644
> --- a/tools/testing/selftests/net/mptcp/mptcp_connect.c
> +++ b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> @@ -72,6 +72,8 @@ static int cfg_wait;
>  static uint32_t cfg_mark;
>  static char *cfg_input;
>  static int cfg_repeat = 1;
> +static int cfg_truncate;
> +static int cfg_rcv_trunc;
>  
>  struct cfg_cmsg_types {
>  	unsigned int cmsg_enabled:1;
> @@ -95,11 +97,15 @@ static struct cfg_sockopt_types cfg_sockopt_types;
>  
>  static void die_usage(void)
>  {
> -	fprintf(stderr, "Usage: mptcp_connect [-6] [-c cmsg] [-i file] [-I num] [-j] [-l] "
> +	fprintf(stderr, "Usage: mptcp_connect [-6] [-c cmsg] [-f offset] [-i file] [-I num] [-j] [-l] "
>  		"[-m mode] [-M mark] [-o option] [-p port] [-P mode] [-j] [-l] [-r num] "
>  		"[-s MPTCP|TCP] [-S num] [-r num] [-t num] [-T num] [-u] [-w sec] connect_address\n");
>  	fprintf(stderr, "\t-6 use ipv6\n");
>  	fprintf(stderr, "\t-c cmsg -- test cmsg type <cmsg>\n");
> +	fprintf(stderr, "\t-f offset -- stop the I/O after receiving and sending the specified amount "
> +		"of bytes. If there are unread bytes in the receive queue, that will cause a MPTCP "
> +		"fastclose at close/shutdown. If offset is negative, expect the peer to close before "
> +		"all the local data as been sent, thus toleration errors on write and EPIPE signals\n");

Just a small typo here that I can fix when applying (if I don't forget):

  s/as/has/

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

  reply	other threads:[~2022-09-09 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  8:49 [PATCH mptcp-next v4 1/3] mptcp: propagate fastclose error Paolo Abeni
2022-09-09  8:49 ` [PATCH mptcp-next v4 2/3] mptcp: use fastclose on more edge scenarios Paolo Abeni
2022-09-09  8:49 ` [PATCH mptcp-next v4 3/3] selftests: mptcp: update and extend fastclose test-cases Paolo Abeni
2022-09-09 15:39   ` Matthieu Baerts [this message]
2022-09-09 16:58     ` Paolo Abeni
2022-09-09 17:21   ` selftests: mptcp: update and extend fastclose test-cases: Tests Results MPTCP CI
2022-09-10  0:21   ` [PATCH mptcp-next v4 3/3] selftests: mptcp: update and extend fastclose test-cases Mat Martineau
2022-09-11 18:23     ` Matthieu Baerts
2022-09-20 14:54       ` Matthieu Baerts
2022-09-21 12:36         ` 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=8b87693f-66a7-67ce-752e-d98df7162552@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@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).