On Tue, 20 Sep 2022 10:12:02 +0200, Bernard Metzler wrote:
> 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.
>
> [...]
Applied, thanks!
[1/1] RDMA/siw: Always consume all skbuf data in sk_data_ready() upcall.
https://git.kernel.org/rdma/rdma/c/754209850df836
Best regards,
--
Leon Romanovsky <leon@xxxxxxxxxx>
