From: Matthieu Baerts <[email protected]> Date: Mon, 21 Sep 2020 16:57:58 +0200
> From: Mat Martineau <[email protected]> > > When receiving a DATA_FIN MPTCP option on a TCP FIN packet, the DATA_FIN > information would be stored but the MPTCP worker did not get > scheduled. In turn, the MPTCP socket state would remain in > TCP_ESTABLISHED and no blocked operations would be awakened. > > TCP FIN packets are seen by the MPTCP socket when moving skbs out of the > subflow receive queues, so schedule the MPTCP worker when a skb with > DATA_FIN but no data payload is moved from a subflow queue. Other cases > (DATA_FIN on a bare TCP ACK or on a packet with data payload) are > already handled. > > Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/84 > Fixes: 43b54c6ee382 ("mptcp: Use full MPTCP-level disconnect state machine") > Acked-by: Paolo Abeni <[email protected]> > Signed-off-by: Mat Martineau <[email protected]> > Signed-off-by: Matthieu Baerts <[email protected]> Applied to 'net', thanks.
