netdev - Re: On TCP_CONGESTION & letter case

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: <20231120093514.24a5bedc@hermes.local>
Date: Mon, 20 Nov 2023 09:35:14 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: rjmcmahon <rjmcmahon@...cmahon.com>
Cc: Netdev <netdev@...r.kernel.org>
Subject: Re: On TCP_CONGESTION & letter case

On Sun, 19 Nov 2023 10:36:03 -0800
rjmcmahon <rjmcmahon@...cmahon.com> wrote:

> Hi all,
> 
> Will the CCA string in setsockopt and getsockopt for TCP_CONGESTION 
> always be lowercase?
> 
> Sorry if this question has been asked and answered somewhere else.
> 
> Thanks,
> Bob
> 

The convention has to always use lower case since this is what is
used by many other places, filesystem types, queue disciplines, etc.
In theory, mixed UglyCamelCase is possible but would end up being
bike shedded during review process.