netdev - Re: [PATCH net-next 4/4] tcp: remove limit on initial receive window

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CANn89iJYh3F+1u8ZVGkhk6nQrN07ub0mkuc8sEzQx9Ta3kbsGQ@mail.gmail.com>
Date:   Tue, 12 Jan 2021 21:56:25 +0100
From:   Eric Dumazet <edumazet@...gle.com>
To:     Heath Caldwell <hcaldwel@...mai.com>
Cc:     netdev <netdev@...r.kernel.org>, Yuchung Cheng <ycheng@...gle.com>,
        Josh Hunt <johunt@...mai.com>, Ji Li <jli@...mai.com>
Subject: Re: [PATCH net-next 4/4] tcp: remove limit on initial receive window

On Tue, Jan 12, 2021 at 9:43 PM Heath Caldwell <hcaldwel@...mai.com> wrote:
>
> On 2021-01-12 21:26 (+0100), Eric Dumazet <edumazet@...gle.com> wrote:

> > This is fine. This has been done forever. Your change might break applications.
>
> In what way might applications be broken?
>
> It seems to be a very strange position to allow a configured maximum to
> be violated because of obscure precedent.
>

Welcome to the real world

Some applications use setsockopt(), followed by getsockopt() to make
sure their change has been recorded.

Some setups might break, you can be sure of this.

I doubt this issue is serious enough, the code has been there forever.

Please fix the documentation (if any)