netdev - Re: Shall we add some note info for tcp_min_snd

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]

Date:   Wed, 3 Jul 2019 11:34:50 +0200
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     ZhangXiao <xiao.zhang@...driver.com>, edumazet@...gle.com,
        davem@...emloft.net
Cc:     netdev@...r.kernel.org
Subject: Re: Shall we add some note info for tcp_min_snd_mss?



On 7/3/19 1:35 AM, ZhangXiao wrote:
> Hi David & Eric,
> 
> Commit 5f3e2bf0 (tcp: add tcp_min_snd_mss sysctl) add a new interface to
> adjust network. While if this variable been set too large, for example
> larger then (MTU - 40), the net link maybe damaged. So, how about adding
> some warning messages for the operator/administrator? In document, or in
> source code.

What kind of warning message do you 
envision exactly ?

The sysctl is global, devices MTU can be quite arbitrary.

Like almost all sysctls, sysadmins are supposed to know what they are doing.