linux-kernel - Re: [PATCH] IPv4/IPv6: update sysctl files

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]

Date:	Wed, 08 Apr 2009 00:18:28 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	shen@...fujitsu.com
Cc:	bhutchings@...arflare.com, akpm@...ux-foundation.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] IPv4/IPv6: update sysctl files

From: Shen Feng <shen@...fujitsu.com>
Date: Wed, 08 Apr 2009 11:28:21 +0800

> 
> 
> on 04/08/2009 10:47 AM, Ben Hutchings wrote:
>> On Wed, 2009-04-08 at 02:39 +0000, Shen Feng wrote:
>>> Now the following sysctl files in /proc/sys/net/ipv4 are used by
>>> both IPv4 and IPv6.
>>> tcp_mem  tcp_rmem  tcp_wmem
>>> udp_mem  udp_rmem_min  udp_wmem_min
>>> Putting them in /proc/sys/net/ipv4 is not a good choice.
>> [...]
>> 
>> But this is part of the ABI to userland.  You cannot remove sysctl files
>> without long advance notice documented in feature-removal-schedule.txt
>> (if at all).
>> 
>> If it is possible to add the paths
>> /proc/sys/net/{tcp,udp} while retaining aliases under /proc/sys/net/ipv4
>> then that might be a workable solution.
> 
> Thanks. That's a good solution.
> 
> But I'm still confused.
> Why not create another tcp_mem in /proc/sys/net/ipv6?

People just need to understand that ipv4 is always going to be
there and that's where all the tcp controls are.

I really am not going to entertain changes that try to move generic
inet sysctl things out of the ipv4 directory.  There is really no
point at all.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/