Thread (6 messages) flat view 6 messages, 3 authors, 2021-11-23

Re: [PATCH net 2/2] net/smc: Ensure the active closing peer first closes clcsock

From: Karsten Graul <hidden>
Date: 2021-11-23 08:36:32
Also in: linux-rdma, linux-s390

On 23/11/2021 09:25, Tony Lu wrote:
The side that actively closed socket, it's clcsock doesn't enter
TIME_WAIT state, but the passive side does it. It should show the same
behavior as TCP sockets.

Consider this, when client actively closes the socket, the clcsock in
server enters TIME_WAIT state, which means the address is occupied and
won't be reused before TIME_WAIT dismissing. If we restarted server, the
service would be unavailable for a long time.

To solve this issue, shutdown the clcsock in [A], perform the TCP active
close progress first, before the passive closed side closing it. So that
the actively closed side enters TIME_WAIT, not the passive one.
Thank you, I will pick this up for our next submission to the net tree.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help