> I think that the problem is a destroy_sock() done at a wrong time.
[snip snip snip]
> This patch seems at least safe to me (but I don' t understand at all the
> TCP code to be sure this is the right patch, and now it' s a bit late
> so I can be wrong...).
[patch snipped]
Your fix appears to be a good one. Laptop has been steadily pounding [1]
my server for 12 hours now with no hiccups. The previous record was 6
hours, and then only if a heavy duty disk job was running on the server.
Without the disk job (as the test is now running) it never lasted longer
than 1.5 hours.
-Mike
[1] being pounded _upon_ by the server is actually more correct.
-
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/