From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: jarkao2@gmail.com, sentiniate@tiscali.it, netdev@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org, olon@verizon.net
Subject: Re: two other cases Re: [Bug 11721] after upgrade to 2.6.27 i cannot navigate
Date: Thu, 23 Oct 2008 14:07:22 -0700 (PDT) [thread overview]
Message-ID: <20081023.140722.193705068.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0810221244390.7072@wrl-59.cs.helsinki.fi>
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Wed, 22 Oct 2008 13:00:01 +0300 (EEST)
> [PATCH] tcp: Restore ordering of TCP options for the sake of inter-operability
>
> This is not our bug! Sadly some devices cannot cope with the change
> of TCP option ordering which was a result of the recent rewrite of
> the option code (not that there was some particular reason steming
> from the rewrite for the reordering) though any ordering of TCP
> options is perfectly legal. Thus we restore the original ordering
> to allow interoperability with/through such broken devices and add
> some warning about this trap. Since the reordering just happened
> without any particular reason, this change shouldn't cost us
> anything.
>
> There are already couple of known failure reports (within close
> proximity of the last release), so the problem might be more
> wide-spread than a single device. And other reports which may
> be due to the same problem though the symptoms were less obvious.
> Analysis of one of the case revealed (with very high probability)
> that sack capability cannot be negotiated as the first option
> (SYN never got a response).
>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
> Reported-by: Aldo Maggi <sentiniate@tiscali.it>
> Tested-by: Aldo Maggi <sentiniate@tiscali.it>
Applied and I'll queue up for -stable, thanks!
prev parent reply other threads:[~2008-10-23 21:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 7:00 two other cases Re: [Bug 11721] after upgrade to 2.6.27 i cannot navigate Aldo Maggi
2008-10-21 7:20 ` Jarek Poplawski
2008-10-21 7:38 ` Aldo Maggi
2008-10-21 7:59 ` Jarek Poplawski
2008-10-21 9:36 ` Ilpo Järvinen
2008-10-21 10:09 ` Jarek Poplawski
2008-10-21 10:51 ` Ilpo Järvinen
2008-10-21 11:12 ` Jarek Poplawski
2008-10-21 12:18 ` Ilpo Järvinen
2008-10-21 12:34 ` Jarek Poplawski
2008-10-21 14:16 ` Ilpo Järvinen
2008-10-21 14:47 ` Aldo Maggi
2008-10-21 16:29 ` Jarek Poplawski
2008-10-21 18:18 ` Aldo Maggi
2008-10-21 18:45 ` Jarek Poplawski
2008-10-21 23:32 ` David Miller
2008-10-22 10:00 ` Ilpo Järvinen
2008-10-22 11:49 ` Aldo Maggi
2008-10-22 12:09 ` Ilpo Järvinen
2008-10-22 13:19 ` Aldo Maggi
2008-10-27 6:51 ` tcp_sack problem " Jarek Poplawski
2008-10-23 21:07 ` David Miller [this message]
[not found] <20081020222914.GB2966@ami.dom.local>
[not found] ` <20081021054903.GA4491@ff.dom.local>
[not found] ` <20081021092721.72ae73ea@topolino>
[not found] ` <20081021074954.GB4715@ff.dom.local>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081023.140722.193705068.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olon@verizon.net \
--cc=sentiniate@tiscali.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).