netdev - Re: [net,v2] tcp: correct handling of extreme memory squeeze

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250127113214.294bcafb@elisabeth>
Date: Mon, 27 Jan 2025 11:32:14 +0100
From: Stefano Brivio <sbrivio@...hat.com>
To: Jason Xing <kerneljasonxing@...il.com>
Cc: Jon Maloy <jmaloy@...hat.com>, Eric Dumazet <edumazet@...gle.com>, Neal
 Cardwell <ncardwell@...gle.com>, netdev@...r.kernel.org,
 davem@...emloft.net, kuba@...nel.org, passt-dev@...st.top,
 lvivier@...hat.com, dgibson@...hat.com, eric.dumazet@...il.com, Menglong
 Dong <menglong8.dong@...il.com>
Subject: Re: [net,v2] tcp: correct handling of extreme memory squeeze

On Mon, 27 Jan 2025 18:17:28 +0800
Jason Xing <kerneljasonxing@...il.com> wrote:

> I'm not that sure if it's a bug belonging to the Linux kernel.

It is, because for at least 20-25 years (before that it's a bit hard to
understand from history) a non-zero window would be announced, as
obviously expected, once there's again space in the receive window.

> The other side not sending a window probe causes this issue...?

It doesn't cause this issue, but it triggers it.

> The other part of me says we cannot break the user's behaviour.

This sounds quite relevant, yes.

-- 
Stefano