Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Bernard Metzler e09caa38e1 RDMA/siw: Always consume all skbuf data in sk_data_ready() upcall. ... [ Upstream commit 754209850df8367c954ac1de7671c7430b1f342c ] 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> Signed-off-by: Sasha Levin <sashal@kernel.org>		2022-10-26 13:22:38 +02:00
..
core	RDMA/cma: Fix arguments order in net device validation	2022-09-15 12:04:55 +02:00
hw	RDMA/mlx5: Set local port to one when accessing counters	2022-09-15 12:04:55 +02:00
sw	RDMA/siw: Always consume all skbuf data in sk_data_ready() upcall.	2022-10-26 13:22:38 +02:00
ulp	RDMA/ib_srp: Fix a deadlock	2022-03-02 11:41:10 +01:00
Kconfig
Makefile