Hi Geliang, Wei,
Recently, we noticed you contributed to the MPTCP Upstream project by
sharing some bug-fixes, thank you for that!
Are you interested to contribute more?
Patches containing new features or any significant code modifications
related to MPTCP are preferably discussed on MPTCP Upstream mailing list
prior to netdev: mptcp(a)lists.01.org
But before working on consequent patches, it is easier to discuss that
on the mailing list. Technical details can be discussed on our IRC
channel. We also have weekly remote meetings to improve the
coordination. We think they are really useful. If the time and/or the
date are an issue for you, please tell us. It is always possible to
change or dedicate some meetings accessible to different time-zones. But
we think the coordination is key to avoid loosing time on conflicting work.
Feel free to reply off-list or on IRC if you are more comfortable with that.
More info: https://github.com/multipath-tcp/mptcp_net-next/wiki
Tessares | Belgium | Hybrid Access Solutions
Currently syncookies on MP_JOIN connections are not handled correctly: the
connections fallback to TCP and are kept alive instead of resetting them at
The first patch propagates the required information up to syn_recv_sock time,
and the 2nd patch addresses the unifying the error path for all MP_JOIN
Paolo Abeni (2):
mptcp: cache msk on MP_JOIN init_req
mptcp: drop MP_JOIN request sock on syn cookies
net/mptcp/protocol.h | 1 +
net/mptcp/subflow.c | 57 +++++++++++++++++++++-----------------------
2 files changed, 28 insertions(+), 30 deletions(-)
Paolo says he prefers direct hooking of SOL_SOCKET instead of copying
values in bind/listen/connect, so do that here.
Similar to the v1 patchset, except that first patch is new (adds
needed 'do not use generic handler' for mptcp sake),
second patch adds minimal SOL_SOCKET support (rest yields -EOPNOTSUPP).
Last patch is almost the same as v1 (only fixes an error check and
extends scope of sk lock).
First patch adds switch to test script so it can be run with a fixed
file size rather than a random one.
Second patch adds receive buffer autotuning. I rebased this on top
of mptcp-next as per Christophs patch suggestion to make sure the
initialisation function has been run for the fallback case too.
I suggest to apply this to mptcp-next so this can be pushed to net-next
once that opens up again.
First patch makes reuseport setsockopt work by copying the mptcp
sockets setting to the newly created subflow socket.
Second patch makes mptcp accept IPV6_V6ONLY by applying the setsockopt
to the initial socket.
First patch addresses:
Second patch makes sshd work with ipv6 too.
I've tested this with out-of-tree patch that aliases IPPROTO_TCP to
IPPROTO_MPTCP, without these patches I see the behaviour Christoph
describes in the github issue (restart fails, IPV6_V6only error).