From: David Howells Date: Thu, 30 Jan 2020 21:50:36 +0000 (+0000) Subject: rxrpc: Fix insufficient receive notification generation X-Git-Tag: v5.15~4547^2~10^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f71dbf2fb28489a79bde0dca1c8adfb9cdb20a6b;p=platform%2Fkernel%2Flinux-starfive.git rxrpc: Fix insufficient receive notification generation In rxrpc_input_data(), rxrpc_notify_socket() is called if the base sequence number of the packet is immediately following the hard-ack point at the end of the function. However, this isn't sufficient, since the recvmsg side may have been advancing the window and then overrun the position in which we're adding - at which point rx_hard_ack >= seq0 and no notification is generated. Fix this by always generating a notification at the end of the input function. Without this, a long call may stall, possibly indefinitely. Fixes: 248f219cb8bc ("rxrpc: Rewrite the data and ack handling code") Signed-off-by: David Howells --- diff --git a/net/rxrpc/input.c b/net/rxrpc/input.c index 96d54e5..ef10fbf 100644 --- a/net/rxrpc/input.c +++ b/net/rxrpc/input.c @@ -599,10 +599,8 @@ ack: false, true, rxrpc_propose_ack_input_data); - if (seq0 == READ_ONCE(call->rx_hard_ack) + 1) { - trace_rxrpc_notify_socket(call->debug_id, serial); - rxrpc_notify_socket(call); - } + trace_rxrpc_notify_socket(call->debug_id, serial); + rxrpc_notify_socket(call); unlock: spin_unlock(&call->input_lock);