Rohit Maheshwari 06f5201c63 net/tls: Fix to avoid gettig invalid tls record ... Current code doesn't check if tcp sequence number is starting from (/after) 1st record's start sequnce number. It only checks if seq number is before 1st record's end sequnce number. This problem will always be a possibility in re-transmit case. If a record which belongs to a requested seq number is already deleted, tls_get_record will start looking into list and as per the check it will look if seq number is before the end seq of 1st record, which will always be true and will return 1st record always, it should in fact return NULL. As part of the fix, start looking each record only if the sequence number lies in the list else return NULL. There is one more check added, driver look for the start marker record to handle tcp packets which are before the tls offload start sequence number, hence return 1st record if the record is tls start marker and seq number is before the 1st record's starting sequence number. Fixes: e8f6979981 ("net/tls: Add generic NIC offload infrastructure") Signed-off-by: Rohit Maheshwari <rohitm@chelsio.com> Reviewed-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>		2020-02-19 16:32:06 -08:00
..
Kconfig
Makefile
tls_device_fallback.c
tls_device.c	net/tls: Fix to avoid gettig invalid tls record	2020-02-19 16:32:06 -08:00
tls_main.c	bpf: Sockmap/tls, push write_space updates through ulp updates	2020-01-15 23:26:13 +01:00
tls_proc.c	net/tls: Fix unused function warning	2019-11-15 12:12:28 -08:00
tls_sw.c	Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf	2020-01-16 10:04:40 +01:00
tls_toe.c
trace.c
trace.h