Re: [PATCH net-next] tcp: correct the skip logic in tcp_sacktag_skip()

[Paolo Abeni <pabeni@redhat.com>]

On 7/13/25 5:22 PM, Xin Guo wrote:
> tcp_sacktag_skip() directly return the input skb only
> if TCP_SKB_CB(skb)->seq>skip_to_seq,
> this is not right, and  the logic should be
> TCP_SKB_CB(skb)->seq>=skip_to_seq, 

Adding Kuniyuki

I'm not sure this statement is actually true. A more clear (and slightly
more descriptive) commit message could help better understanding the
issue. What is the bad behaviour you are observing?

Ideally a packetdrill test case to demonstrate it would help

> for example
> if start_seq is equal to tcp_highest_sack_seq() ,
> the start_seq is equal to seq of skb which is from
> tcp_highest_sack().
> and on the other side ,when
> tcp_highest_sack_seq() < start_seq in
> tcp_sacktag_write_queue(),
> the skb is from tcp_highest_sack() will be ignored
> in tcp_sacktag_skip(), so clean the logic also.
> 
> Fixes: 75c119afe14f ("tcp: implement rb-tree based retransmit queue")

At very least the fixes tag looks wrong, because AFAICS such change did
not modify the behaviour tcp_sacktag_skip.

> Signed-off-by: Xin Guo <guoxin0309@gmail.com>

Thanks,

Paolo