From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: brian.vowell@gmail.com, akpm@linux-foundation.org,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 10767] New: Seg Fault Instead of Swapping
Date: Tue, 03 Jun 2008 16:35:18 -0700 (PDT) [thread overview]
Message-ID: <20080603.163518.153888925.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0805261349510.16829@wrl-59.cs.helsinki.fi>
From: "Ilpo_Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Mon, 26 May 2008 14:24:33 +0300 (EEST)
Ilpo, do you want me to apply this to net-2.6?
> [PATCH] [TCP]: Fix inconsistency source (CA_Open only when !tcp_left_out(tp))
>
> It is possible that this skip path causes TCP to end up into an
> invalid state where ca_state was left to CA_Open while some
> segments already came into sacked_out. If next valid ACK doesn't
> contain new SACK information TCP fails to enter into
> tcp_fastretrans_alert(). Thus at least high_seq is set
> incorrectly to a too high seqno because some new data segments
> could be sent in between (and also, limited transmit is not
> being correctly invoked there). Reordering in both directions
> can easily cause this situation to occur.
>
> I guess we would want to use tcp_moderate_cwnd(tp) there as well
> as it may be possible to use this to trigger oversized burst to
> network by sending an old ACK with huge amount of SACK info, but
> I'm a bit unsure about its effects (mainly to FlightSize), so to
> be on the safe side I just currently fixed it minimally to keep
> TCP's state consistent (obviously, such nasty ACKs have been
> possible this far). Though it seems that FlightSize is already
> underestimated by some amount, so probably on the long term we
> might want to trigger recovery there too, if appropriate, to make
> FlightSize calculation to resemble reality at the time when the
> losses where discovered (but such change scares me too much now
> and requires some more thinking anyway how to do that as it
> likely involves some code shuffling).
>
> This bug was found by Brian Vowell while running my TCP debug
> patch to find cause of another TCP issue (fackets_out
> miscount).
>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
next prev parent reply other threads:[~2008-06-03 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10767-10286@http.bugzilla.kernel.org/>
2008-05-21 17:57 ` [Bugme-new] [Bug 10767] New: Seg Fault Instead of Swapping Andrew Morton
[not found] ` <cf4145200805211140o3b2287dcsc57f8a78aa48a99d@mail.gmail.com>
2008-05-21 18:53 ` Andrew Morton
2008-05-21 20:18 ` Ilpo Järvinen
[not found] ` <cf4145200805211345y3b00d209o58e11a7b553cdfc6@mail.gmail.com>
2008-05-23 10:25 ` Ilpo Järvinen
[not found] ` <cf4145200805230906k34a0452at773e840b791e6b0a@mail.gmail.com>
[not found] ` <cf4145200805231024w2e735fb8ifecf7e2e1bab5957@mail.gmail.com>
2008-05-23 18:01 ` Ilpo Järvinen
[not found] ` <cf4145200805231126y401c2454w97e5305346aa8acd@mail.gmail.com>
2008-05-24 8:57 ` Ilpo Järvinen
[not found] ` <cf4145200805240706p2eb54e9ei51bc33f782ff5aef@mail.gmail.com>
2008-05-26 11:24 ` Ilpo Järvinen
2008-06-03 23:35 ` David Miller [this message]
2008-06-04 7:12 ` Ilpo Järvinen
2008-06-04 18:20 ` David Miller
2008-05-26 11:33 ` Ilpo Järvinen
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=20080603.163518.153888925.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=brian.vowell@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
/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).