[DCCP]: Set RTO for newly created child socket
This mirrors a recent change in tcp_open_req_child, whereby the icsk_rto of the newly created child socket was not set (but rather on the parent socket). Same fix for DCCP. Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
4d46861be6
commit
99c72ce091
|
@ -103,7 +103,7 @@ struct sock *dccp_create_openreq_child(struct sock *sk,
|
||||||
|
|
||||||
if (newsk != NULL) {
|
if (newsk != NULL) {
|
||||||
const struct dccp_request_sock *dreq = dccp_rsk(req);
|
const struct dccp_request_sock *dreq = dccp_rsk(req);
|
||||||
struct inet_connection_sock *newicsk = inet_csk(sk);
|
struct inet_connection_sock *newicsk = inet_csk(newsk);
|
||||||
struct dccp_sock *newdp = dccp_sk(newsk);
|
struct dccp_sock *newdp = dccp_sk(newsk);
|
||||||
struct dccp_minisock *newdmsk = dccp_msk(newsk);
|
struct dccp_minisock *newdmsk = dccp_msk(newsk);
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue