From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B92C5367F5F; Tue, 3 Feb 2026 05:57:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770098250; cv=none; b=F0KzrwADopqN1lX0c2nPPt8K1w1E7U8Ipqol89aCu+cJlH3fyGzm3F9s3K8XorJNxYH7sVWG6uBcfk73eit5i3nuUO2wrtCLQEJrmVTTtAedBfWc1btD3q/7/eUSl/rcgoIqS1oSPrwyrizCglnS/zL+ptumitJS8h7PwCY7LZ0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770098250; c=relaxed/simple; bh=h4t6CKlu7x8fZ7JonwTHLu30EuoT2G+8oJphjmZ0WHo=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=jJ/meYpdvfhMW9Sdvp2z2FKK9PNd7XRWvym5lIq3FCEPhH9QKXo7URdTfpKUXI0+pvbVvVTCXpd/KjQTsB1xBGmeZxcs3PyCu3hx0XnC4y8gkqjzpQkyLsRJcBaqLXUSj1O9oyXbbL5rKfnPcGGUyO64SdHvqCY/z7Wv5OGfIeY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NyUJrQp/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="NyUJrQp/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D2662C116D0; Tue, 3 Feb 2026 05:57:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770098250; bh=h4t6CKlu7x8fZ7JonwTHLu30EuoT2G+8oJphjmZ0WHo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=NyUJrQp/ruUhVtx9mQKYDGRN5R8SdC66R1CNxpvOMvCloMeZlYXQTT6dNC3qvsmEO DDqTc7KmTkvcsNhnA5XaBuI2Fx/If+WMjL47Ev5+11PUznJ6Yc1/9I/x2eh0IhMCjO uPfxmBVlOpB7GfGcCKsHscS6bZi+cZYCjoOPyZvfj6g1/bsQPXhrODzIK377UPlXcp reFZNHc5NQfsojLZxAwR/OPOWkdMilT6Vc3IoBe8EeEuSpzRwCWMWDKvnUoK+DW3Le h+UqxWULlGupP5fFSgviMQb66HUxyajg7aePyjic5IjeDL6Zlw7zO1VTdjIRLhbPr+ EFTr5WQrIGjeg== From: Allison Henderson To: netdev@vger.kernel.org Cc: linux-kselftest@vger.kernel.org, pabeni@redhat.com, edumazet@google.com, rds-devel@oss.oracle.com, kuba@kernel.org, horms@kernel.org, linux-rdma@vger.kernel.org, allison.henderson@oracle.com Subject: [PATCH net-next v5 4/8] net/rds: Kick-start TCP receiver after accept Date: Mon, 2 Feb 2026 22:57:19 -0700 Message-ID: <20260203055723.1085751-5-achender@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20260203055723.1085751-1-achender@kernel.org> References: <20260203055723.1085751-1-achender@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: Gerd Rausch In cases where the server (the node with the higher IP-address) in an RDS/TCP connection is overwhelmed it is possible that the socket that was just accepted is chock-full of messages, up to the limit of what the socket receive buffer permits. Subsequently, "rds_tcp_data_ready" won't be called anymore, because there is no more space to receive additional messages. Nor was it called prior to the point of calling "rds_tcp_set_callbacks", because the "sk_data_ready" pointer didn't even point to "rds_tcp_data_ready" yet. We fix this by simply kick-starting the receive-worker for all cases where the socket state is neither "TCP_CLOSE_WAIT" nor "TCP_CLOSE". Signed-off-by: Gerd Rausch Signed-off-by: Allison Henderson --- net/rds/tcp_listen.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/rds/tcp_listen.c b/net/rds/tcp_listen.c index 492dcc6568bf..b5786227623c 100644 --- a/net/rds/tcp_listen.c +++ b/net/rds/tcp_listen.c @@ -291,6 +291,8 @@ int rds_tcp_accept_one(struct rds_tcp_net *rtn) new_sock->sk->sk_state == TCP_LAST_ACK || new_sock->sk->sk_state == TCP_CLOSE) rds_conn_path_drop(cp, 0); + else + queue_delayed_work(cp->cp_wq, &cp->cp_recv_w, 0); new_sock = NULL; ret = 0; -- 2.43.0