MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-net] mptcp: fix DATA_FIN generation on early shutdown.
Date: Fri, 12 Feb 2021 17:06:55 -0800	[thread overview]
Message-ID: <6525cc44-63f-655b-453a-2c8d8219f0bf@linux.intel.com> (raw)
In-Reply-To: 23fa447e02e5b0a342408a2065d15281c223e32b.1613081583.git.pabeni@redhat.com

[-- Attachment #1: Type: text/plain, Size: 4648 bytes --]


On Thu, 11 Feb 2021, Paolo Abeni wrote:

> If the msk is closed before sending or receiving any data,
> no DATA_FIN is generated, instead an MPC ack packet is
> crafted out.
>
> In the above scenario, the MPTCP protocol create and send a
> pure ack and such packets matches also the criteria for an
> MPC ack and the protocol tries first to insert MPC options,
> leading the described error.
>
> This change address the issue skipping MPC option for DATA_FIN
> packets or if the subflow is not established.
>
> To avoid doing multiple times the same test, fetch the data_fin
> flag in a bool variable and pass it to both the interested
> helpers.
>
> Fixes: 6d0060f600ad ("mptcp: Write MPTCP DSS headers to outgoing data packets")
> Signed-off-by: Paolo Abeni <pabeni(a)redhat.com>
> ---
> The scenario is tested by a specific pktdrill tested,
> already pushed
> ---
> net/mptcp/options.c | 23 ++++++++++++++---------
> 1 file changed, 14 insertions(+), 9 deletions(-)

Hi Paolo -

Change looks good to me:

Reviewed-by: Mat Martineau <mathew.j.martineau(a)linux.intel.com>

Were you intending this for the export branch or the -net tree? (Unsure 
due to the [PATCH mptcp-net] prefix)


Thanks,

Mat



>
> diff --git a/net/mptcp/options.c b/net/mptcp/options.c
> index b63574d6b812e..444a38681e93e 100644
> --- a/net/mptcp/options.c
> +++ b/net/mptcp/options.c
> @@ -411,6 +411,7 @@ static void clear_3rdack_retransmission(struct sock *sk)
> }
>
> static bool mptcp_established_options_mp(struct sock *sk, struct sk_buff *skb,
> +					 bool snd_data_fin_enable,
> 					 unsigned int *size,
> 					 unsigned int remaining,
> 					 struct mptcp_out_options *opts)
> @@ -428,9 +429,10 @@ static bool mptcp_established_options_mp(struct sock *sk, struct sk_buff *skb,
> 	if (!skb)
> 		return false;
>
> -	/* MPC/MPJ needed only on 3rd ack packet */
> -	if (subflow->fully_established ||
> -	    subflow->snd_isn != TCP_SKB_CB(skb)->seq)
> +	/* MPC/MPJ needed only on 3rd ack packet, DATA_FIN and TCP shutdown take precedence */
> +	if (subflow->fully_established || snd_data_fin_enable ||
> +	    subflow->snd_isn != TCP_SKB_CB(skb)->seq ||
> +	    sk->sk_state != TCP_ESTABLISHED)
> 		return false;
>
> 	if (subflow->mp_capable) {
> @@ -502,20 +504,20 @@ static void mptcp_write_data_fin(struct mptcp_subflow_context *subflow,
> }
>
> static bool mptcp_established_options_dss(struct sock *sk, struct sk_buff *skb,
> +					  bool snd_data_fin_enable,
> 					  unsigned int *size,
> 					  unsigned int remaining,
> 					  struct mptcp_out_options *opts)
> {
> 	struct mptcp_subflow_context *subflow = mptcp_subflow_ctx(sk);
> 	struct mptcp_sock *msk = mptcp_sk(subflow->conn);
> -	u64 snd_data_fin_enable, ack_seq;
> 	unsigned int dss_size = 0;
> 	struct mptcp_ext *mpext;
> 	unsigned int ack_size;
> 	bool ret = false;
> +	u64 ack_seq;
>
> 	mpext = skb ? mptcp_get_ext(skb) : NULL;
> -	snd_data_fin_enable = mptcp_data_fin_enabled(msk);
>
> 	if (!skb || (mpext && mpext->use_map) || snd_data_fin_enable) {
> 		unsigned int map_size;
> @@ -717,12 +719,15 @@ bool mptcp_established_options(struct sock *sk, struct sk_buff *skb,
> 			       unsigned int *size, unsigned int remaining,
> 			       struct mptcp_out_options *opts)
> {
> +	struct mptcp_subflow_context *subflow = mptcp_subflow_ctx(sk);
> +	struct mptcp_sock *msk = mptcp_sk(subflow->conn);
> 	unsigned int opt_size = 0;
> +	bool snd_data_fin;
> 	bool ret = false;
>
> 	opts->suboptions = 0;
>
> -	if (unlikely(mptcp_check_fallback(sk)))
> +	if (unlikely(__mptcp_check_fallback(msk)))
> 		return false;
>
> 	/* prevent adding of any MPTCP related options on reset packet
> @@ -731,10 +736,10 @@ bool mptcp_established_options(struct sock *sk, struct sk_buff *skb,
> 	if (unlikely(skb && TCP_SKB_CB(skb)->tcp_flags & TCPHDR_RST))
> 		return false;
>
> -	if (mptcp_established_options_mp(sk, skb, &opt_size, remaining, opts))
> +	snd_data_fin = mptcp_data_fin_enabled(msk);
> +	if (mptcp_established_options_mp(sk, skb, snd_data_fin, &opt_size, remaining, opts))
> 		ret = true;
> -	else if (mptcp_established_options_dss(sk, skb, &opt_size, remaining,
> -					       opts))
> +	else if (mptcp_established_options_dss(sk, skb, snd_data_fin, &opt_size, remaining, opts))
> 		ret = true;
>
> 	/* we reserved enough space for the above options, and exceeding the
> -- 
> 2.26.2
> _______________________________________________
> mptcp mailing list -- mptcp(a)lists.01.org
> To unsubscribe send an email to mptcp-leave(a)lists.01.org
>

--
Mat Martineau
Intel

             reply	other threads:[~2021-02-13  1:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13  1:06 Mat Martineau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-15  9:44 [MPTCP] Re: [PATCH mptcp-net] mptcp: fix DATA_FIN generation on early shutdown Paolo Abeni
2021-02-15 15:29 Matthieu Baerts
2021-02-15 19:10 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=6525cc44-63f-655b-453a-2c8d8219f0bf@linux.intel.com \
    --to=mptcp@lists.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