Ayush Sawal 1be15667db cxgb4/chtls/cxgbit: Keeping the max ofld immediate data size same in cxgb4 and ulds ... [ Upstream commit 2355a6773a2cb0d2dce13432dde78497f1d6617b ] The Max imm data size in cxgb4 is not similar to the max imm data size in the chtls. This caused an mismatch in output of is_ofld_imm() of cxgb4 and chtls. So fixed this by keeping the max wreq size of imm data same in both chtls and cxgb4 as MAX_IMM_OFLD_TX_DATA_WR_LEN. As cxgb4's max imm. data value for ofld packets is changed to MAX_IMM_OFLD_TX_DATA_WR_LEN. Using the same in cxgbit also. Fixes: 36bedb3f2e ("crypto: chtls - Inline TLS record Tx") Signed-off-by: Ayush Sawal <ayush.sawal@chelsio.com> Acked-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sasha Levin <sashal@kernel.org>		2021-03-04 09:39:36 +01:00
..
chtls_cm.c	chtls: Fix potential resource leak	2021-02-13 13:51:14 +01:00
chtls_cm.h	cxgb4/chtls/cxgbit: Keeping the max ofld immediate data size same in cxgb4 and ulds	2021-03-04 09:39:36 +01:00
chtls_hw.c	chelsio/chtls: fix a double free in chtls_setkey()	2020-12-08 10:18:54 +01:00
chtls_io.c	chelsio/chtls: fix tls record info to user	2020-11-05 11:08:32 +01:00
chtls_main.c
chtls.h
Makefile