netdev - Re: [PATCH net-next] tcp: remove SOCK_QUEUE

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: <20200914.133613.2303200671140457460.davem@davemloft.net>
Date:   Mon, 14 Sep 2020 13:36:13 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     edumazet@...gle.com
Cc:     netdev@...r.kernel.org, eric.dumazet@...il.com, soheil@...gle.com
Subject: Re: [PATCH net-next] tcp: remove SOCK_QUEUE_SHRUNK

From: Eric Dumazet <edumazet@...gle.com>
Date: Mon, 14 Sep 2020 03:20:27 -0700

> SOCK_QUEUE_SHRUNK is currently used by TCP as a temporary state
> that remembers if some room has been made in the rtx queue
> by an incoming ACK packet.
> 
> This is later used from tcp_check_space() before
> considering to send EPOLLOUT.
> 
> Problem is: If we receive SACK packets, and no packet
> is removed from RTX queue, we can send fresh packets, thus
> moving them from write queue to rtx queue and eventually
> empty the write queue.
> 
> This stall can happen if TCP_NOTSENT_LOWAT is used.
> 
> With this fix, we no longer risk stalling sends while holes
> are repaired, and we can fully use socket sndbuf.
> 
> This also removes a cache line dirtying for typical RPC
> workloads.
> 
> Fixes: c9bee3b7fdec ("tcp: TCP_NOTSENT_LOWAT socket option")
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>

Applied, thanks Eric.