tree e2f6baf2552d5b844763d09d7430010183be80d6
parent 1a09404a2338163f181d170c7abdc2242b6c6f03
author Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> 1190312885 -0700
committer David S. Miller <davem@sunset.davemloft.net> 1192060328 -0700

[TCP]: Maintain highest_sack accurately to the highest skb

In general, it should not be necessary to call tcp_fragment for
already SACKed skbs, but it's better to be safe than sorry. And
indeed, it can be called from sacktag when a DSACK arrives or
some ACK (with SACK) reordering occurs (sacktag could be made
to avoid the call in the latter case though I'm not sure if it's
worth of the trouble and added complexity to cover such marginal
case).

The collapse case has return for SACKED_ACKED case earlier, so
just WARN_ON if internal inconsistency is detected for some
reason.

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>