tcp: fix comment for tp->highest_sack
There was an off-by-one error in the comments describing the highest_sack field in struct tcp_sock. The comments previously claimed that it was the "start sequence of the highest skb with SACKed bit". This commit fixes the comments to note that it is the "start sequence of the skb just *after* the highest skb with SACKed bit". Signed-off-by: Neal Cardwell <ncardwell@google.com> Acked-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
eea79e0713
commit
ecb9719236
@@ -412,7 +412,8 @@ struct tcp_sock {
|
||||
|
||||
struct tcp_sack_block recv_sack_cache[4];
|
||||
|
||||
struct sk_buff *highest_sack; /* highest skb with SACK received
|
||||
struct sk_buff *highest_sack; /* skb just after the highest
|
||||
* skb with SACKed bit set
|
||||
* (validity guaranteed only if
|
||||
* sacked_out > 0)
|
||||
*/
|
||||
|
Reference in New Issue
Block a user