[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200102.154305.639050830505824860.davem@davemloft.net>
Date: Thu, 02 Jan 2020 15:43:05 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: yangpc@...gsu.com
Cc: edumazet@...gle.com, kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
ast@...nel.org, daniel@...earbox.net, kafai@...com,
songliubraving@...com, yhs@...com, andriin@...com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tcp: fix "old stuff" D-SACK causing SACK to be treated
as D-SACK
From: Pengcheng Yang <yangpc@...gsu.com>
Date: Mon, 30 Dec 2019 17:54:41 +0800
> When we receive a D-SACK, where the sequence number satisfies:
> undo_marker <= start_seq < end_seq <= prior_snd_una
> we consider this is a valid D-SACK and tcp_is_sackblock_valid()
> returns true, then this D-SACK is discarded as "old stuff",
> but the variable first_sack_index is not marked as negative
> in tcp_sacktag_write_queue().
>
> If this D-SACK also carries a SACK that needs to be processed
> (for example, the previous SACK segment was lost), this SACK
> will be treated as a D-SACK in the following processing of
> tcp_sacktag_write_queue(), which will eventually lead to
> incorrect updates of undo_retrans and reordering.
>
> Fixes: fd6dad616d4f ("[TCP]: Earlier SACK block verification & simplify access to them")
> Signed-off-by: Pengcheng Yang <yangpc@...gsu.com>
Applied and queued up for -stable, thank you.
Powered by blists - more mailing lists