[lkml]   [2006]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.17: networking bug??
    Linus Torvalds wrote:
    > On Tue, 13 Jun 2006, John Heffner wrote:
    >> The best thing you can do is try to find this broken box and inform its owner
    >> that it needs to be fixed. (If you can find out what it is, I'd be interested
    >> to know.) In the meantime, disabling window scaling will work around the
    >> problem for you.
    > Well, arguably, we shouldn't necessarily have defaults that use window
    > scaling, or we should have ways to recognize automatically when it
    > doesn't work (which may not be possible).
    > It's not like there aren't broken boxes out there, and it might be better
    > to make the default buffer sizes just be low enough that window scaling
    > simply isn't an issue.
    > I suspect that the people who really want/need window scaling know about
    > it, and could be assumed to know enough to raise their limits, no?

    Agreed. It's taken me over a month here to realize that the particular
    webserver in question ( wasn't "dead", but merely being
    blocked by my 2.6.17 kernel. All was fine with 2.6.16, as I discovered today.

    I wonder how many other "dead sites" there are out there,
    that will be shut off from people when they "upgrade" to 2.6.17 ?

    I'm a kernel hacker. Most users of 2.6.17 will not be.
    The default should be something that works "by default".

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-06-13 20:28    [W:0.020 / U:13.152 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site