| commit | c60ce4e265404ca42ba860401f4b0f1e97332a67 | |
| author | Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> | |
| Thu, 14 Oct 2010 01:52:09 +0000 (14 01:52 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Sun, 17 Oct 2010 20:46:33 +0000 (17 13:46 -0700) | ||
| tree | 7a71a183c1512e32257f9ec66d74e8544c772bec | treesnapshot (tar.gz zip) |
| parent | 1fdb936101637c91819efea47e921bb592e07e34 | commitdiff |
tcp: use correct counters in CA_CWR state too
As CWR is stronger than CA_Disorder state, we can miscount
SACK/Reno failure into other timeouts. Not a bad problem as
it can happen only due to ECN, FRTO detecting spurious RTO
or xmit error which are the only callers of tcp_enter_cwr.
And even then losses and RTO must still follow thereafter
to actually end up into the relevant code paths.
Compile tested.
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
As CWR is stronger than CA_Disorder state, we can miscount
SACK/Reno failure into other timeouts. Not a bad problem as
it can happen only due to ECN, FRTO detecting spurious RTO
or xmit error which are the only callers of tcp_enter_cwr.
And even then losses and RTO must still follow thereafter
to actually end up into the relevant code paths.
Compile tested.
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
| net/ipv4/tcp_timer.c | diffblobblamehistory |