Bernard Metzler 754209850d RDMA/siw: Always consume all skbuf data in sk_data_ready() upcall. ... For header and trailer/padding processing, siw did not consume new skb data until minimum amount present to fill current header or trailer structure, including potential payload padding. Not consuming any data during upcall may cause a receive stall, since tcp_read_sock() is not upcalling again if no new data arrive. A NFSoRDMA client got stuck at RDMA Write reception of unaligned payload, if the current skb did contain only the expected 3 padding bytes, but not the 4 bytes CRC trailer. Expecting 4 more bytes already arrived in another skb, and not consuming those 3 bytes in the current upcall left the Write incomplete, waiting for the CRC forever. Fixes: 8b6a361b8c ("rdma/siw: receive path") Reported-by: Olga Kornievskaia <kolga@netapp.com> Tested-by: Olga Kornievskaia <kolga@netapp.com> Signed-off-by: Bernard Metzler <bmt@zurich.ibm.com> Link: https://lore.kernel.org/r/20220920081202.223629-1-bmt@zurich.ibm.com Signed-off-by: Leon Romanovsky <leon@kernel.org>		2022-09-20 21:21:18 +03:00
..
core	IB/cm: Refactor cm_insert_listen() and cm_find_listen()	2022-08-30 12:14:23 +03:00
hw	IB/hfi1: remove rc_only_opcode and uc_only_opcode declarations	2022-09-20 20:13:10 +03:00
sw	RDMA/siw: Always consume all skbuf data in sk_data_ready() upcall.	2022-09-20 21:21:18 +03:00
ulp	RDMA/srpt: Use flex array destination for memcpy()	2022-09-20 15:05:29 +03:00
Kconfig	RDMA/erdma: Add driver to kernel build environment	2022-07-27 16:04:05 -03:00
Makefile