> resolve (do a tcp_v4_lookup) again and as a result
> end up sending a RST back to the client.
Please, send some tcpdump showing the problem.
> Can someone tell me if its a known bug and if there is a
> patch ?
...
> Does anyone have any comments or am I missing something
> completely in this one ?
It is difficult to say. The place is dangerous, the problem
is real, really showed and has been fixed in 2.3.
But I still do not see how it is possible in 2.2.
Packet is checked against list of requests when it falls
to listening socket and correct established socket is found there.
When accept() removes open request from queue, real socket is
already in big hash table, so that there is no race window.
Probably, it is me who missed something though...
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/