Its a bug. I've also been sent a possible fix for it if you want it. Its
sufficiently hard to cause (needs to be local) and peculiar I've got the fix
scheduled for 2.0.38pre1. "Fixing" a TCP bug this close to .37 is likely to
be bad engineering decision 8)
-
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/