[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220515140001.cws3pgz4iaaanpjo@m.mifar.in>
Date: Sun, 15 May 2022 17:04:32 +0300
From: Sami Farin <hvtaifwkbgefbaei@...il.com>
To: Linux Networking Mailing List <netdev@...r.kernel.org>
Subject: sockets staying in FIN-WAIT-1, CLOSING, or LAST-ACK state till reboot
Hello,
with 5.15.37, ss -K -t does not properly kill the TCP sockets.
[ Disclaimer: this is my guess of the culprit. I also use wireguard. ]
tcp FIN-WAIT-1 0 1 80.220.8.55:22384 91.198.174.208:443 ino:0 sk:510b cgroup:unreachable:6c46 ---
skmem:(r0,rb87380,t0,tb130560,f0,w0,o0,bl0,d0) ts sack ecn ecnseen bbr wscale:9,10 rto:3744 rtt:33.364/18.714 ato:40 mss:36 pmtu:68 rcvmss:536 advmss:1448 cwnd:1 bytes_sent:701 bytes_acked:702 bytes_received:254 segs_out:6 segs_in:3 data_segs_out:2 data_segs_in:1 bbr:(bw:10176bps,mrtt:27.924,pacing_gain:2.88672,cwnd_gain:2.88672) send 8632bps lastsnd:601107881 lastrcv:601107884 lastack:601107810 pacing_rate 11658680bps delivery_rate 10192bps delivered:3 app_limited busy:23371222ms lost:1 rcv_space:14480 rcv_ssthresh:42242 minrtt:27.924
$ nc -l -p 22384
Ncat: bind to 0.0.0.0:22384: Address already in use. QUITTING.
$ nc -l 127.0.0.1 22384
^C
$
These zombie sockets all have Send-Q > 0.
--
Do what you love because life is too short for anything else.
Powered by blists - more mailing lists