rs maybe fetch wrong clientip

[baochun]

this maybe happend in this condition:

connection1: rsip + 80  <---> localip1+port1, clientip1 ; this connection not expire in ip_vs_ca, but free in lvs. 
connection2: rsip + 3306 <---> localip1 + port1 , clientip2 ; and this is new connection.

if this happend, connection2 will get clientip1.

[yubo]

Indeed there is such a possibility,
Do you have a good idea?
I think we can do a coverage strategy to solve this problem

[CentUser]

I think the root cause of this problem is that this code saves connection info in module allocated memory, and when a connection is up abnormally, one could not know when the connection info should be removed from the hash table if the connection is closed due to the previous reason.
Original toa module use the sk_user_data to store the client info, but the 8 bit variable is not sufficient for ipv6.

[CentUser]

Trade memory for speed, if we could maintain an slab cache for connections and hack into the tcp_prot->destroy function, at there release the connection info.