On 07 Jan 2015, at 21:33, Eric Dumazet <eric.duma...@gmail.com> wrote: > On Wed, 2015-01-07 at 20:37 +0000, Erik Grinaker wrote: > I agree. I have contacted Amazon about this, but am not too hopeful >> for a quick fix; they have been promising SACK-support on their >> loadbalancers since 2006, for example. >> >> That said, since this change breaks a service as popular as S3, it >> might be worth reconsidering. > > Which change are you talking about ? Have you done a bisection to > clearly identify the patch exposing this sender bug ?
FWIW, I've done a bisection, and it’s triggered by this change: https://github.com/torvalds/linux/commit/4e4f1fc226816905c937f9b29dabe351075dfe0f > We are not going to stick TCP stack to 20th century and buggy peers or > middleboxes, sorry. That’s fair enough.-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
