All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliangtang@gmail.com>
Cc: mptcp@lists.linux.dev, Geliang Tang <geliangtang@xiaomi.com>
Subject: Re: [MPTCP][PATCH v7 mptcp-next 0/5] MP_FAIL support
Date: Tue, 3 Aug 2021 17:42:30 -0700 (PDT)	[thread overview]
Message-ID: <d345bd98-3b46-50bf-5e20-3ec28e4eda41@linux.intel.com> (raw)
In-Reply-To: <cover.1627547666.git.geliangtang@xiaomi.com>

On Thu, 29 Jul 2021, Geliang Tang wrote:

> From: Geliang Tang <geliangtang@xiaomi.com>
>
> v7:
> - The single subflow case is handled by sending MP_FAIL + RST instead
>   of sending MP_FAIL echo.
>

Hi Geliang -

I ran some tests using your checksum test patch, and verified the single 
subflow behavior. So I think this looks good for the export branch:

Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>


Thanks,

Mat


> v6: only rebased patch 1
> - move the struct member 'fail_seq' behind 'ext_copy'.
> - define OPTION_MPTCP_FAIL to BIT(12), BIT(11) is used by DSS
> - move the MP_FAIL writing code at the beginning of mptcp_write_options,
>   and add the 'unlikely' tag.
> - tag: export/20210728T080904
>
> v5:
> - patch 1, change "ret = true;" to "return true;"
> - patch 3, in the single-subflow case, send MP_FAIL and receive the
>   echo, then temporarily handled by reset.
>
> v4:
> - just deal with the multiple subflows case, put the single subflow
>   case into the new 'infinite mapping' part.
>
> v3:
> - respond with MP_FAIL
> - add single subflow check
> - add infinite mapping sending and receiving
> - export/20210626T054902
>
> v2:
> - MP_FAIL logic:
>   * Peer B send a DSS to peer A, and the data has been modify by the
>  middleboxes, then peer A detects the bad checksum.
>   * In the multiple subflows case, peer A sends MP_FAIL+RST back to peer B,
>  and peer A discards the data following the bad data sequence number. Peer
>  B receives this MP_FAIL+RST, and close this subflow.
>   * In the single subflow case, using the simple implementation, peer A
>  sends MP_FAIL back to peer B, and peer A fallback to a regular TCP. Peer
>  B receives this MP_FAIL, and fallback to a regular TCP.
>
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/52
>
> Geliang Tang (5):
>  mptcp: MP_FAIL suboption sending
>  mptcp: MP_FAIL suboption receiving
>  mptcp: send out MP_FAIL when data checksum fails
>  mptcp: add the mibs for MP_FAIL
>  selftests: mptcp: add MP_FAIL mibs check
>
> include/net/mptcp.h                           |  5 +-
> net/mptcp/mib.c                               |  2 +
> net/mptcp/mib.h                               |  2 +
> net/mptcp/options.c                           | 76 ++++++++++++++++++-
> net/mptcp/pm.c                                |  5 ++
> net/mptcp/protocol.h                          | 19 +++++
> net/mptcp/subflow.c                           | 16 ++++
> .../testing/selftests/net/mptcp/mptcp_join.sh | 38 ++++++++++
> 8 files changed, 158 insertions(+), 5 deletions(-)
>
> -- 
> 2.31.1
>
>
>

--
Mat Martineau
Intel

  parent reply	other threads:[~2021-08-04  0:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  8:40 [MPTCP][PATCH v7 mptcp-next 0/5] MP_FAIL support Geliang Tang
2021-07-29  8:40 ` [MPTCP][PATCH v7 mptcp-next 1/5] mptcp: MP_FAIL suboption sending Geliang Tang
2021-07-29  8:40   ` [MPTCP][PATCH v7 mptcp-next 2/5] mptcp: MP_FAIL suboption receiving Geliang Tang
2021-07-29  8:40     ` [MPTCP][PATCH v7 mptcp-next 3/5] mptcp: send out MP_FAIL when data checksum fails Geliang Tang
2021-07-29  8:40       ` [MPTCP][PATCH v7 mptcp-next 4/5] mptcp: add the mibs for MP_FAIL Geliang Tang
2021-07-29  8:40         ` [MPTCP][PATCH v7 mptcp-next 5/5] selftests: mptcp: add MP_FAIL mibs check Geliang Tang
2021-08-04  0:42 ` Mat Martineau [this message]
2021-08-04  8:52 ` [MPTCP][PATCH v7 mptcp-next 0/5] MP_FAIL support 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=d345bd98-3b46-50bf-5e20-3ec28e4eda41@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=geliangtang@gmail.com \
    --cc=geliangtang@xiaomi.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.