Mat Martineau 6d37a0b857 mptcp: Only send DATA_FIN with final mapping ... When a DATA_FIN is sent in a MPTCP DSS option that contains a data mapping, the DATA_FIN consumes one byte of space in the mapping. In this case, the DATA_FIN should only be included in the DSS option if its sequence number aligns with the end of the mapped data. Otherwise the subflow can send an incorrect implicit sequence number for the DATA_FIN, and the DATA_ACK for that sequence number would not close the MPTCP-level connection correctly. Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2020-03-03 17:01:43 -08:00
..
crypto.c	mptcp: move from sha1 (v0) to sha256 (v1)	2020-01-24 13:44:08 +01:00
ctrl.c	mptcp: new sysctl to control the activation per NS	2020-01-24 13:44:08 +01:00
Kconfig	mptcp: select CRYPTO	2020-02-16 19:37:16 -08:00
Makefile	mptcp: new sysctl to control the activation per NS	2020-01-24 13:44:08 +01:00
options.c	mptcp: Only send DATA_FIN with final mapping	2020-03-03 17:01:43 -08:00
protocol.c	mptcp: Use per-subflow storage for DATA_FIN sequence number	2020-03-03 17:01:43 -08:00
protocol.h	mptcp: Use per-subflow storage for DATA_FIN sequence number	2020-03-03 17:01:43 -08:00
subflow.c	mptcp: avoid work queue scheduling if possible	2020-02-26 20:46:26 -08:00
token.c	mptcp: Add key generation and token tree	2020-01-24 13:44:07 +01:00