Until now, while processing CONN_ACK message the socket wakeup is called when the check for congestion returns true. This is incorrect.
In this commit, we call the socket wakeup only if congestion is released in CONN_ACK message processing path. Signed-off-by: Parthasarathy Bhuvaragan <[email protected]> --- net/tipc/socket.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/tipc/socket.c b/net/tipc/socket.c index bb5875c18c98..7383fe261fe5 100644 --- a/net/tipc/socket.c +++ b/net/tipc/socket.c @@ -801,7 +801,7 @@ static void tipc_sk_proto_rcv(struct tipc_sock *tsk, struct sk_buff *skb) } else if (mtyp == CONN_ACK) { conn_cong = tsk_conn_cong(tsk); tsk->sent_unacked -= msg_msgcnt(hdr); - if (conn_cong) + if (!conn_cong) sk->sk_write_space(sk); } else if (mtyp != CONN_PROBE_REPLY) { pr_warn("Received unknown CONN_PROTO msg\n"); -- 2.1.4 ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
