[PATCH mptcp-next v7 0/4] Clarify when options can be used

Matthieu Baerts posted 4 patches 7 months, 3 weeks ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/20211230191651.1831507-1-matthieu.baerts@tessares.net
There is a newer version of this series
Maintainers: Matthieu Baerts <matthieu.baerts@tessares.net>, "David S. Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, Mat Martineau <mathew.j.martineau@linux.intel.com>
net/mptcp/options.c | 94 ++++++++++++++++++++++++++++++++-------------
1 file changed, 67 insertions(+), 27 deletions(-)
[PATCH mptcp-next v7 0/4] Clarify when options can be used
Posted by Matthieu Baerts 7 months, 3 weeks ago
This is a new version of Geliang's series called "send MP_FAIL with MP_RST and
others".

The Squash-to patch is the same as the draft I previously sent but fixing a
compilation issue: MP_RST can be sent with MP_FASTCLOSE and MP_FAIL but
MP_FASTCLOSE cannot be sent with MP_FAIL.

Patch 2/4 has not been modified.

Here, you might want to start looking at "mptcp: clarify when options can be
used" and check if everything is OK for you related to when options can be used
together.

If this is OK, the logic behind the Squash-to patch should be OK. Of course, the
implementation might not be OK but that's different :)

Patch 4/4 is there just to have mptcp_established_options() in sync with
mptcp_write_options() (and the RFC).

Happy New Year!

Geliang Tang (2):
  Squash to "mptcp: implement fastclose xmit path"
  mptcp: print out reset infos of MP_RST

Matthieu Baerts (2):
  mptcp: clarify when options can be used
  mptcp: allow sending both ADD_ADDR and RM_ADDR

 net/mptcp/options.c | 94 ++++++++++++++++++++++++++++++++-------------
 1 file changed, 67 insertions(+), 27 deletions(-)

-- 
2.33.1