[MPTCP] Re: [PATCH mptcp-next 0/3] mptcp: add fastclose option

[Florian Westphal <fw at strlen.de>]

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

Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> On 25/11/2020 18:49, Florian Westphal wrote:
> > I plan to hold the MPTCP reset patches back for the time being until
> > netlink + mptcpd are aware of its existence.
> 
> I certainly missed something here but are you here talking about MP_TCPRST
> support? Or still about the send of fast-close?

Oh, no, I jumped off the fastclose train here.  This is only wrt. MP_TCPRST.
Another approach would be to add the *send side* for tcprst first,
perhaps it helps with tcpdump deciphering.

But for RX there is really no point when the kernel can't pass that
information along to a consumer such as mptcpd.

> If it is about fast-close, why netlink + mptcpd needs to be aware first?
> Could we eventually send fast-close when the userspace app (here using
> packetdrill format) does this:
> 
>     setsockopt(<fd>, SOL_SOCKET, SO_LINGER, {onoff=1, linger=0}, 8);
>     close(<fd>);
> 
> (if we accept this socket option)
> No rush of course, just in case these patches were already written :)

Yes, I think it might make sense to allow userspace to generate a
fastclose at will.

The last iteration I sent autogenerated a fastclose for the 'unread data
in socket queue when userspace called close' case, which is analogous to
what the linux TCP stack does when you close with unread data in the
local socket.

But I think extending it to linger makes sense as well.