tcp: completely support active reset
Subsystems (3)
v2 cover tcp: completely support active reset
From: Jason Xing <[email protected]>
This time the patch series finally covers all the cases in the active reset logic. After this, we can know the related exact reason(s).
v2
1. use RFC 9293 in the comment and changelog instead of old RFC 793
2. correct the comment and changelog in patch 5
Jason Xing (6):
tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_CLOSE for active
reset
tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_LINGER for active
reset
tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_MEMORY for active
reset
tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
tcp: rstreason: introduce SK_RST_REASON_TCP_TIMEOUT for active reset
tcp: rstreason: let it work finally in tcp_send_active_reset()
include/net/rstreason.h | 32 ++++++++++++++++++++++++++++++++ net/ipv4/tcp.c | 10 +++++----- net/ipv4/tcp_output.c | 2 +- net/ipv4/tcp_timer.c | 6 +++--- 4 files changed, 41 insertions(+), 9 deletions(-)
Signature · 1 line
2.37.3
PATCH v2 1/6 tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_CLOSE for active reset
From: Jason Xing <[email protected]>
Introducing a new type TCP_ABORT_ON_CLOSE for tcp reset reason to handle the case where more data is unread in closing phase.
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-)
include/net/rstreason.h +6 -0
@@ -17,6 +17,7 @@ FN(TCP_ABORT_ON_DATA) \ FN(TCP_TIMEWAIT_SOCKET) \ FN(INVALID_SYN) \ + FN(TCP_ABORT_ON_CLOSE) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \
@@ -84,6 +85,11 @@ enum sk_rst_reason {* an error, send a reset" */ SK_RST_REASON_INVALID_SYN , +/** +* @SK_RST_REASON_TCP_ABORT_ON_CLOSE: abort on close +* corresponding to LINUX_MIB_TCPABORTONCLOSE +*/ + SK_RST_REASON_TCP_ABORT_ON_CLOSE,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to
net/ipv4/tcp.c +1 -1
@@ -2833,7 +2833,7 @@ void __tcp_close(struct sock *sk, long timeout)NET_INC_STATS (sock_net (sk),LINUX_MIB_TCPABORTONCLOSE );tcp_set_state (sk,TCP_CLOSE );tcp_send_active_reset (sk, sk->sk_allocation, -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_ABORT_ON_CLOSE ); }else if (sock_flag (sk,SOCK_LINGER ) && !sk->sk_lingertime) {/* Check zero linger _after_ checking for unread data. */ sk->sk_prot->disconnect (sk,0 );
Signature · 1 line
2.37.3
PATCH v2 2/6 tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_LINGER for active reset
In reply to Jason XingFrom: Jason Xing <[email protected]>
Introducing a new type TCP_ABORT_ON_LINGER for tcp reset reason to handle negative linger value case.
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-)
include/net/rstreason.h +6 -0
@@ -18,6 +18,7 @@ FN(TCP_TIMEWAIT_SOCKET) \ FN(INVALID_SYN) \ FN(TCP_ABORT_ON_CLOSE) \ + FN(TCP_ABORT_ON_LINGER) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \
@@ -90,6 +91,11 @@ enum sk_rst_reason {* corresponding to LINUX_MIB_TCPABORTONCLOSE */ SK_RST_REASON_TCP_ABORT_ON_CLOSE , +/** +* @SK_RST_REASON_TCP_ABORT_ON_LINGER: abort on linger +* corresponding to LINUX_MIB_TCPABORTONLINGER +*/ + SK_RST_REASON_TCP_ABORT_ON_LINGER,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to
net/ipv4/tcp.c +1 -1
@@ -2908,7 +2908,7 @@ void __tcp_close(struct sock *sk, long timeout)if (READ_ONCE (tp->linger2) <0 ) {tcp_set_state (sk,TCP_CLOSE );tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_ABORT_ON_LINGER );__NET_INC_STATS (sock_net (sk),LINUX_MIB_TCPABORTONLINGER ); }else {
Signature · 1 line
2.37.3
PATCH v2 3/6 tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_MEMORY for active reset
In reply to Jason XingFrom: Jason Xing <[email protected]>
Introducing a new type TCP_ABORT_ON_MEMORY for tcp reset reason to handle out of memory case.
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 2 +- net/ipv4/tcp_timer.c | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-)
include/net/rstreason.h +6 -0
@@ -19,6 +19,7 @@ FN(INVALID_SYN) \ FN(TCP_ABORT_ON_CLOSE) \ FN(TCP_ABORT_ON_LINGER) \ + FN(TCP_ABORT_ON_MEMORY) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \
@@ -96,6 +97,11 @@ enum sk_rst_reason {* corresponding to LINUX_MIB_TCPABORTONLINGER */ SK_RST_REASON_TCP_ABORT_ON_LINGER , +/** +* @SK_RST_REASON_TCP_ABORT_ON_MEMORY: abort on memory +* corresponding to LINUX_MIB_TCPABORTONMEMORY +*/ + SK_RST_REASON_TCP_ABORT_ON_MEMORY,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to
net/ipv4/tcp.c +1 -1
@@ -2927,7 +2927,7 @@ void __tcp_close(struct sock *sk, long timeout)if (tcp_check_oom (sk,0 )) {tcp_set_state (sk,TCP_CLOSE );tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_ABORT_ON_MEMORY );__NET_INC_STATS (sock_net (sk),LINUX_MIB_TCPABORTONMEMORY ); }else if (!check_net (sock_net (sk))) {
net/ipv4/tcp_timer.c +1 -1
@@ -125,7 +125,7 @@ static int tcp_out_of_resources(struct sock *sk, bool do_reset) do_reset = true;if (do_reset)tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_ABORT_ON_MEMORY );tcp_done (sk);__NET_INC_STATS (sock_net (sk),LINUX_MIB_TCPABORTONMEMORY );return 1 ;
Signature · 1 line
2.37.3
PATCH v2 4/6 tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
In reply to Jason XingFrom: Jason Xing <[email protected]>
Introducing a new type TCP_STATE to handle some reset conditions appearing in RFC 793 due to its socket state. Actually, we can look into RFC 9293 which has no discrepancy about this part.
---
V2
1. use RFC 9293 instead of RFC 793 which is too old (Kuniyuki)
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 4 ++-- net/ipv4/tcp_timer.c | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-)
include/net/rstreason.h +6 -0
@@ -20,6 +20,7 @@ FN(TCP_ABORT_ON_CLOSE) \ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ + FN(TCP_STATE) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \
@@ -102,6 +103,11 @@ enum sk_rst_reason {* corresponding to LINUX_MIB_TCPABORTONMEMORY */ SK_RST_REASON_TCP_ABORT_ON_MEMORY , +/** +* @SK_RST_REASON_TCP_STATE: abort on tcp state +* Please see RFC 9293 for all possible reset conditions +*/ + SK_RST_REASON_TCP_STATE,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to
net/ipv4/tcp.c +2 -2
@@ -3031,7 +3031,7 @@ int tcp_disconnect(struct sock *sk, int flags)/* The last check adjusts for discrepancy of Linux wrt. RFC * states */ -tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_NOT_SPECIFIED ); +tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_TCP_STATE );WRITE_ONCE (sk->sk_err,ECONNRESET ); }else if (old_state ==TCP_SYN_SENT )WRITE_ONCE (sk->sk_err,ECONNRESET );
@@ -4649,7 +4649,7 @@ int tcp_abort(struct sock *sk, int err)if (!sock_flag (sk,SOCK_DEAD )) {if (tcp_need_reset (sk->sk_state))tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_STATE );tcp_done_with_error (sk, err); }
net/ipv4/tcp_timer.c +1 -1
@@ -779,7 +779,7 @@ static void tcp_keepalive_timer (struct timer_list *t) goto out; } } -tcp_send_active_reset (sk,GFP_ATOMIC ,SK_RST_REASON_NOT_SPECIFIED ); +tcp_send_active_reset (sk,GFP_ATOMIC ,SK_RST_REASON_TCP_STATE ); goto death; }
Signature · 1 line
2.37.3
PATCH v2 5/6 tcp: rstreason: introduce SK_RST_REASON_TCP_TIMEOUT for active reset
In reply to Jason XingFrom: Jason Xing <[email protected]>
Whether user sets TCP_USER_TIMEOUT option or not, when we find there is no left chance to proceed, we will send an RST to the other side.
---
v2
1. correct the comment and changelog
--- include/net/rstreason.h | 8 ++++++++ net/ipv4/tcp_timer.c | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-)
include/net/rstreason.h +8 -0
@@ -21,6 +21,7 @@ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ FN(TCP_STATE) \ + FN(TCP_TIMEOUT) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \
@@ -108,6 +109,13 @@ enum sk_rst_reason {* Please see RFC 9293 for all possible reset conditions */ SK_RST_REASON_TCP_STATE , +/** +* @SK_RST_REASON_TCP_TIMEOUT: time to timeout +* Whether user sets TCP_USER_TIMEOUT options or not, when we +* have already run out of all the chances, we have to reset the +* connection +*/ + SK_RST_REASON_TCP_TIMEOUT,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to
net/ipv4/tcp_timer.c +1 -1
@@ -807,7 +807,7 @@ static void tcp_keepalive_timer (struct timer_list *t) (user_timeout == 0 && icsk->icsk_probes_out >= keepalive_probes(tp))) {tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_TIMEOUT );tcp_write_err (sk); goto out; }
Signature · 1 line
2.37.3
PATCH v2 6/6 tcp: rstreason: let it work finally in tcp_send_active_reset()
In reply to Jason XingFrom: Jason Xing <[email protected]>
Now it's time to let it work by using the 'reason' parameter in the trace world :)
--- net/ipv4/tcp_output.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv4/tcp_output.c +1 -1
@@ -3649,7 +3649,7 @@ void tcp_send_active_reset(struct sock *sk, gfp_t priority,/* skb of trace_tcp_send_reset() keeps the skb that caused RST, * skb here is different to the troublesome skb, so use NULL */ -trace_tcp_send_reset (sk,NULL ,SK_RST_REASON_NOT_SPECIFIED ); +trace_tcp_send_reset (sk,NULL , reason); }/* Send a crossed SYN-ACK during socket establishment.
Signature · 1 line
2.37.3
Re: [PATCH net-next v2 1/6] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_CLOSE for active reset
In reply to Jason XingQuoted 7 lines · Jason Xing
From: Jason Xing <[email protected]>
Introducing a new type
TCP_ABORT_ON_CLOSEfor tcp reset reason to handle the case where more data is unread in closing phase.Signed-off-by Jason Xing <[email protected]>
Re: [PATCH net-next v2 2/6] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_LINGER for active reset
In reply to Jason XingQuoted 7 lines · Jason Xing
From: Jason Xing <[email protected]>
Introducing a new type
TCP_ABORT_ON_LINGERfor tcp reset reason to handle negative linger value case.Signed-off-by Jason Xing <[email protected]>
Re: [PATCH net-next v2 3/6] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_MEMORY for active reset
In reply to Jason XingQuoted 7 lines · Jason Xing
From: Jason Xing <[email protected]>
Introducing a new type
TCP_ABORT_ON_MEMORYfor tcp reset reason to handle out of memory case.Signed-off-by Jason Xing <[email protected]>
Re: [PATCH net-next v2 4/6] tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
In reply to Jason XingQuoted 47 lines · Jason Xing
From: Jason Xing <[email protected]>
Introducing a new type
TCP_STATEto handle some reset conditions appearing in RFC 793 due to its socket state. Actually, we can look into RFC 9293 which has no discrepancy about this part.Signed-off-by Jason Xing <[email protected]>---
V21. use RFC 9293 instead of RFC 793 which is too old (Kuniyuki)
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 4 ++-- net/ipv4/tcp_timer.c | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-)include/net/rstreason.h +6
-0@@ -20,6 +20,7 @@ FN(TCP_ABORT_ON_CLOSE) \ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ + FN(TCP_STATE) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \@@ -102,6 +103,11 @@ enum sk_rst_reason {* corresponding to LINUX_MIB_TCPABORTONMEMORY */ SK_RST_REASON_TCP_ABORT_ON_MEMORY , +/** +* @SK_RST_REASON_TCP_STATE: abort on tcp state +* Please see RFC 9293 for all possible reset conditions +*/ + SK_RST_REASON_TCP_STATE,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to net/ipv4/tcp.c +0
-0
net/ipv4/tcp.c int tcp_disconnect(struct sock *sk, int flags) · line 3034
Quoted 5 lines
net/ipv4/tcp.c +1
-1@@ -3031,7 +3031,7 @@ int tcp_disconnect(struct sock *sk, int flags)/* The last check adjusts for discrepancy of Linux wrt. RFC * states */ -tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_NOT_SPECIFIED ); +tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_TCP_STATE );
I disagree with this. tcp_disconnect() is initiated by the user.
You are conflating two possible conditions :
1) tcp_need_reset(old_state)
2) (tp->snd_nxt != tp->write_seq && (1 << old_state) & (TCPF_CLOSING | TCPF_LAST_ACK)))
Quoted 28 lines
net/ipv4/tcp.c +1
-1WRITE_ONCE (sk->sk_err,ECONNRESET ); }else if (old_state ==TCP_SYN_SENT )WRITE_ONCE (sk->sk_err,ECONNRESET );@@ -4649,7 +4649,7 @@ int tcp_abort(struct sock *sk, int err)if (!sock_flag (sk,SOCK_DEAD )) {if (tcp_need_reset (sk->sk_state))tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_STATE );tcp_done_with_error (sk, err); }net/ipv4/tcp_timer.c +1
-2@@ -779,7 +779,7 @@ static void tcp_keepalive_timer (struct timer_list *t) goto out; } } -tcp_send_active_reset (sk,GFP_ATOMIC ,SK_RST_REASON_NOT_SPECIFIED ); +tcp_send_active_reset (sk,GFP_ATOMIC ,SK_RST_REASON_TCP_STATE ); goto death; } --2.37.3
Re: [PATCH net-next v2 5/6] tcp: rstreason: introduce SK_RST_REASON_TCP_TIMEOUT for active reset
In reply to Jason XingQuoted 6 lines · Jason Xing
From: Jason Xing <[email protected]>
Whether user sets
TCP_USER_TIMEOUToption or not, when we find there is no left chance to proceed, we will send an RST to the other side.
Not sure why you mention TCP_USER_TIMEOUT here.
Quoted 50 lines
Signed-off-by Jason Xing <[email protected]>---
v21. correct the comment and changelog
--- include/net/rstreason.h | 8 ++++++++ net/ipv4/tcp_timer.c | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-)include/net/rstreason.h +8
-0@@ -21,6 +21,7 @@ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ FN(TCP_STATE) \ + FN(TCP_TIMEOUT) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \@@ -108,6 +109,13 @@ enum sk_rst_reason {* Please see RFC 9293 for all possible reset conditions */ SK_RST_REASON_TCP_STATE , +/** +* @SK_RST_REASON_TCP_TIMEOUT: time to timeout +* Whether user sets TCP_USER_TIMEOUT options or not, when we +* have already run out of all the chances, we have to reset the +* connection +*/ + SK_RST_REASON_TCP_TIMEOUT,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to net/ipv4/tcp_timer.c +1
-2@@ -807,7 +807,7 @@ static void tcp_keepalive_timer (struct timer_list *t) (user_timeout == 0 && icsk->icsk_probes_out >= keepalive_probes(tp))) {tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_TIMEOUT );tcp_write_err (sk); goto out; } --
Quoted 2 lines
2.37.3
This is more about keepalive really. You should use a better name reflecting that it is a keepalive timeout.
Re: [PATCH net-next v2 5/6] tcp: rstreason: introduce SK_RST_REASON_TCP_TIMEOUT for active reset
Hello Eric,
Quoted 58 lines · Eric Dumazet
Quoted 6 lines · Jason Xing
From: Jason Xing <[email protected]>
Whether user sets
TCP_USER_TIMEOUToption or not, when we find there is no left chance to proceed, we will send an RST to the other side.Not sure why you mention
TCP_USER_TIMEOUThere.Quoted 47 lines
Signed-off-by Jason Xing <[email protected]>---
v21. correct the comment and changelog
--- include/net/rstreason.h | 8 ++++++++ net/ipv4/tcp_timer.c | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-)include/net/rstreason.h +8
-0@@ -21,6 +21,7 @@ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ FN(TCP_STATE) \ + FN(TCP_TIMEOUT) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \@@ -108,6 +109,13 @@ enum sk_rst_reason {* Please see RFC 9293 for all possible reset conditions */ SK_RST_REASON_TCP_STATE , +/** +* @SK_RST_REASON_TCP_TIMEOUT: time to timeout +* Whether user sets TCP_USER_TIMEOUT options or not, when we +* have already run out of all the chances, we have to reset the +* connection +*/ + SK_RST_REASON_TCP_TIMEOUT,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to net/ipv4/tcp_timer.c +1
-1@@ -807,7 +807,7 @@ static void tcp_keepalive_timer (struct timer_list *t) (user_timeout == 0 && icsk->icsk_probes_out >= keepalive_probes(tp))) {tcp_send_active_reset (sk,GFP_ATOMIC , -SK_RST_REASON_NOT_SPECIFIED ); +SK_RST_REASON_TCP_TIMEOUT );tcp_write_err (sk);
Quoted 8 lines
Quoted 5 lines
net/ipv4/tcp_timer.c +0
-1goto out; } --2.37.3
This is more about keepalive really. You should use a better name reflecting that it is a keepalive timeout.
I think you're right. Let me use 'TCP_KEEPALIVE_TIMEOUT' then.
Thanks,
Jason
Re: [PATCH net-next v2 4/6] tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
In reply to Eric DumazetHello Eric,
Quoted 57 lines · Eric Dumazet
Quoted 47 lines · Jason Xing
From: Jason Xing <[email protected]>
Introducing a new type
TCP_STATEto handle some reset conditions appearing in RFC 793 due to its socket state. Actually, we can look into RFC 9293 which has no discrepancy about this part.Signed-off-by Jason Xing <[email protected]>---
V21. use RFC 9293 instead of RFC 793 which is too old (Kuniyuki)
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 4 ++-- net/ipv4/tcp_timer.c | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-)include/net/rstreason.h +6
-0@@ -20,6 +20,7 @@ FN(TCP_ABORT_ON_CLOSE) \ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ + FN(TCP_STATE) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \@@ -102,6 +103,11 @@ enum sk_rst_reason {* corresponding to LINUX_MIB_TCPABORTONMEMORY */ SK_RST_REASON_TCP_ABORT_ON_MEMORY , +/** +* @SK_RST_REASON_TCP_STATE: abort on tcp state +* Please see RFC 9293 for all possible reset conditions +*/ + SK_RST_REASON_TCP_STATE,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to net/ipv4/tcp.c +0
-0net/ipv4/tcp.c int tcp_disconnect(struct sock *sk, int flags) · line 3034
Quoted 5 lines
net/ipv4/tcp.c +1
-1@@ -3031,7 +3031,7 @@ int tcp_disconnect(struct sock *sk, int flags)/* The last check adjusts for discrepancy of Linux wrt. RFC * states */ -tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_NOT_SPECIFIED ); +tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_TCP_STATE );I disagree with this.
tcp_disconnect()is initiated by the user.
Quoted 3 lines
You are conflating two possible conditions :
1)
tcp_need_reset(old_state)
For this one, I can keep the TCP_STATE reason, right?
Quoted 3 lines
2) (
tp->snd_nxt!=tp->write_seq&& (1 <<old_state) & (TCPF_CLOSING|TCPF_LAST_ACK)))
For this one, I wonder if I need to separate this condition with 'tcp_need_reset()' and put it into another 'else-if' branch? I decided to name it as 'CLOSE_WITH_DATA' because it can reflect that the write queue of the socket is not empty (at this time the user may think he has more data to send) but it stays in the active close state.
How about it?
Thanks,
Jason
Re: [PATCH net-next v2 4/6] tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
Quoted 61 lines · Jason Xing
Hello Eric,
Quoted 57 lines · Eric Dumazet
Quoted 47 lines · Jason Xing
From: Jason Xing <[email protected]>
Introducing a new type
TCP_STATEto handle some reset conditions appearing in RFC 793 due to its socket state. Actually, we can look into RFC 9293 which has no discrepancy about this part.Signed-off-by Jason Xing <[email protected]>---
V21. use RFC 9293 instead of RFC 793 which is too old (Kuniyuki)
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 4 ++-- net/ipv4/tcp_timer.c | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-)include/net/rstreason.h +6
-0@@ -20,6 +20,7 @@ FN(TCP_ABORT_ON_CLOSE) \ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ + FN(TCP_STATE) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \@@ -102,6 +103,11 @@ enum sk_rst_reason {* corresponding to LINUX_MIB_TCPABORTONMEMORY */ SK_RST_REASON_TCP_ABORT_ON_MEMORY , +/** +* @SK_RST_REASON_TCP_STATE: abort on tcp state +* Please see RFC 9293 for all possible reset conditions +*/ + SK_RST_REASON_TCP_STATE,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to net/ipv4/tcp.c +0
-0net/ipv4/tcp.c int tcp_disconnect(struct sock *sk, int flags) · line 3034
Quoted 5 lines
net/ipv4/tcp.c +1
-1@@ -3031,7 +3031,7 @@ int tcp_disconnect(struct sock *sk, int flags)/* The last check adjusts for discrepancy of Linux wrt. RFC * states */ -tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_NOT_SPECIFIED ); +tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_TCP_STATE );I disagree with this.
tcp_disconnect()is initiated by the user.
Quoted 5 lines
Quoted 3 lines
You are conflating two possible conditions :
1)
tcp_need_reset(old_state)For this one, I can keep the
TCP_STATEreason, right?
What does it mean ?
Quoted 5 lines
Quoted 4 lines
2) (
tp->snd_nxt!=tp->write_seq&& (1 <<old_state) & (TCPF_CLOSING|TCPF_LAST_ACK)))
Quoted 7 lines
For this one, I wonder if I need to separate this condition with '
tcp_need_reset()' and put it into another 'else-if' branch? I decided to name it as 'CLOSE_WITH_DATA' because it can reflect that the write queue of the socket is not empty (at this time the user may think he has more data to send) but it stays in the active close state.
How about it?
This is not CLOSE_WITH_DATA, but a disconnect() operation, initiated by user space.
If we add RST reasons, can we please be careful about the chosen names ?
man connect
<quote>
Some protocol sockets (e.g., TCP sockets as well as datagram
sockets in the UNIX and Internet domains) may dissolve the association by connecting to an address with the sa_family member of sockaddr set to AF_UNSPEC; thereafter, the socket can be connected to another ad‐
dress. (AF_UNSPEC is supported since Linux 2.2.)
</quote>
Very different from close()...
Re: [PATCH net-next v2 4/6] tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
Hello Eric,
Quoted 63 lines · Eric Dumazet
Quoted 61 lines · Jason Xing
Hello Eric,
Quoted 57 lines · Eric Dumazet
Quoted 47 lines · Jason Xing
From: Jason Xing <[email protected]>
Introducing a new type
TCP_STATEto handle some reset conditions appearing in RFC 793 due to its socket state. Actually, we can look into RFC 9293 which has no discrepancy about this part.Signed-off-by Jason Xing <[email protected]>---
V21. use RFC 9293 instead of RFC 793 which is too old (Kuniyuki)
--- include/net/rstreason.h | 6 ++++++ net/ipv4/tcp.c | 4 ++-- net/ipv4/tcp_timer.c | 2 +- 3 files changed, 9 insertions(+), 3 deletions(-)include/net/rstreason.h +6
-0@@ -20,6 +20,7 @@ FN(TCP_ABORT_ON_CLOSE) \ FN(TCP_ABORT_ON_LINGER) \ FN(TCP_ABORT_ON_MEMORY) \ + FN(TCP_STATE) \ FN(MPTCP_RST_EUNSPEC) \ FN(MPTCP_RST_EMPTCP) \ FN(MPTCP_RST_ERESOURCE) \@@ -102,6 +103,11 @@ enum sk_rst_reason {* corresponding to LINUX_MIB_TCPABORTONMEMORY */ SK_RST_REASON_TCP_ABORT_ON_MEMORY , +/** +* @SK_RST_REASON_TCP_STATE: abort on tcp state +* Please see RFC 9293 for all possible reset conditions +*/ + SK_RST_REASON_TCP_STATE,/* Copy from include/uapi/linux/mptcp.h. * These reset fields will not be changed since they adhere to net/ipv4/tcp.c +0
-0net/ipv4/tcp.c int tcp_disconnect(struct sock *sk, int flags) · line 3034
Quoted 5 lines
net/ipv4/tcp.c +1
-1@@ -3031,7 +3031,7 @@ int tcp_disconnect(struct sock *sk, int flags)/* The last check adjusts for discrepancy of Linux wrt. RFC * states */ -tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_NOT_SPECIFIED ); +tcp_send_active_reset (sk,gfp_any (),SK_RST_REASON_TCP_STATE );I disagree with this.
tcp_disconnect()is initiated by the user.
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
You are conflating two possible conditions :
1)
tcp_need_reset(old_state)For this one, I can keep the
TCP_STATEreason, right?What does it mean ?
I mean I wonder if I can use the TCP_STATE reason in tcp_abort() and tcp_disconnect() when tcp_need_reset() returns true?
Quoted 14 lines
Quoted 6 lines
Quoted 5 lines
2) (
tp->snd_nxt!=tp->write_seq&& (1 <<old_state) & (TCPF_CLOSING|TCPF_LAST_ACK)))Quoted 7 lines
For this one, I wonder if I need to separate this condition with '
tcp_need_reset()' and put it into another 'else-if' branch? I decided to name it as 'CLOSE_WITH_DATA' because it can reflect that the write queue of the socket is not empty (at this time the user may think he has more data to send) but it stays in the active close state.
How about it?
Quoted 3 lines
This is not
CLOSE_WITH_DATA, but adisconnect()operation, initiated by user space.
If we add RST reasons, can we please be careful about the chosen names ?
Yes, I know, but like old days, I'm struggling with the English name. Sorry.
Quoted 11 lines
man connect
<quote>
Some protocol sockets (e.g., TCP sockets as well as datagram
sockets in the UNIX and Internet domains) may dissolve the association by connecting to an address with thesa_familymember of sockaddr set toAF_UNSPEC; thereafter, the socket can be connected to another ad‐
dress. (AF_UNSPECis supported since Linux 2.2.)
</quote>
Quoted 1 line
Very different from
close()...
Oh, I see. What I was talking about 'CLOSE' is the socket state, but you are right: the name will finally be displayed to users, which must clearly reflect the real meaning of the underlying behavior.
I will use "TCP_DISCONNECT_WITH_DATA" instead under this condition. And then, I will put it into a new patch since it's a different reason name.
Thanks for your help!
Jason