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 v5 mptcp-next 0/5] MP_FAIL support
Date: Tue, 27 Jul 2021 17:27:15 -0700 (PDT) [thread overview]
Message-ID: <80cc102e-39d8-f779-866e-5772ed2a9f@linux.intel.com> (raw)
In-Reply-To: <cover.1627281326.git.geliangtang@xiaomi.com>
On Mon, 26 Jul 2021, Geliang Tang wrote:
> From: Geliang Tang <geliangtang@xiaomi.com>
>
> 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.
>
Hi Geliang -
Thanks for the v5 changes. The changes are looking good in terms of manual
code review. Since the selftest changes in patch 5 only confirm that
MP_FAIL was not sent, I'm going to do some testing tomorrow to force
checksum failures in single and multiple subflow cases so I can check some
packet traces. It would be good to have some packetdrill checksum test
cases to cover that, but we don't yet.
- Mat
> 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 | 78 ++++++++++++++++++-
> net/mptcp/pm.c | 20 +++++
> net/mptcp/protocol.h | 20 +++++
> net/mptcp/subflow.c | 18 +++++
> .../testing/selftests/net/mptcp/mptcp_join.sh | 38 +++++++++
> 8 files changed, 178 insertions(+), 5 deletions(-)
>
> --
> 2.31.1
>
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2021-07-28 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 6:45 [MPTCP][PATCH v5 mptcp-next 0/5] MP_FAIL support Geliang Tang
2021-07-26 6:45 ` [MPTCP][PATCH v5 mptcp-next 1/5] mptcp: MP_FAIL suboption sending Geliang Tang
2021-07-26 6:45 ` [MPTCP][PATCH v5 mptcp-next 2/5] mptcp: MP_FAIL suboption receiving Geliang Tang
2021-07-26 6:45 ` [MPTCP][PATCH v5 mptcp-next 3/5] mptcp: send out MP_FAIL when data checksum fails Geliang Tang
2021-07-26 6:45 ` [MPTCP][PATCH v5 mptcp-next 4/5] mptcp: add the mibs for MP_FAIL Geliang Tang
2021-07-26 6:45 ` [MPTCP][PATCH v5 mptcp-next 5/5] selftests: mptcp: add MP_FAIL mibs check Geliang Tang
2021-07-26 11:10 ` [MPTCP][PATCH v5 mptcp-next 1/5] mptcp: MP_FAIL suboption sending Paolo Abeni
2021-07-28 2:43 ` Geliang Tang
2021-07-28 0:27 ` Mat Martineau [this message]
2021-07-28 3:04 ` [MPTCP][PATCH v5 mptcp-next 0/5] MP_FAIL support Geliang Tang
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=80cc102e-39d8-f779-866e-5772ed2a9f@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 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).