On 3/3/23 01:09, Florian Westphal wrote:
Which one? As far as I can see TCP stack would end up adding a duplicate quadruple to the hash if we only drop the reference and keep the listen sk around.
I just thought that tcp_timewait_state_process is called by TCP stack to handle TW state, which actually call inet_twsk_deschedule_put parallel to tproxy and that would be the root cause of the deadlock. So I guess now, basically we would leak away the tw socket if we do not call put in tproxy?
