netdev - Re: [PATCH net-next v2 0/2] tcp: save flowlabel and use for receiver repathing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20231004163253.75584412@kernel.org>
Date: Wed, 4 Oct 2023 16:32:53 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: David Morley <morleyd.kernel@...il.com>
Cc: David Miller <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 netdev@...r.kernel.org, David Morley <morleyd@...gle.com>
Subject: Re: [PATCH net-next v2 0/2] tcp: save flowlabel and use for
 receiver repathing

On Fri, 29 Sep 2023 21:03:50 +0000 David Morley wrote:
> This patch series stores the last received ipv6 flowlabel. This last
> received flowlabel is then used to help decide whether a packet is
> likely an RTO retransmit or the result of a TLP. This new information
> is used to better inform the flowlabel change decision for data
> receivers.

Minor conflict with Eric's changes to derive delack_max from rto_min.
This no longer builds, please rebase & resend, thanks!
-- 
pw-bot: cr