netdev - Re: route/max_size sysctl in ipv4

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: <1420683594.5947.43.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Wed, 07 Jan 2015 18:19:54 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Ani Sinha <ani@...sta.com>
Cc:	David Miller <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: route/max_size sysctl in ipv4

On Wed, 2015-01-07 at 17:25 -0800, Ani Sinha wrote:
> hey guys,
> 
> On Tue, Jan 6, 2015 at 5:56 PM, Ani Sinha <ani@...sta.com> wrote:
> > On Mon, Jan 5, 2015 at 4:51 PM, David Miller <davem@...emloft.net> wrote:
> >
> >> The sysctl is kept so that scripts reading it don't suddenly stop
> >> working.  We can't just remove sysctl values.
> >
> > Interestingly, one of our scripts did break. It broke because now this
> > sysctl is only available in the global net namespace and not in the
> > child namespaces. If not breaking scripts is the fundamental logic in
> > keeping in sysctl intact, would you guys be open to accepting a patch
> > where we make this sysctl available for all net namespaces?
> 
> Any thoughts on this?

AFAIK, this sysctl (and others) always have been global.

Only /proc/sys/net/ipv4/route/flush is per ns

namespaces usage can indeed remove some sysctl :
Only initial namespace show them.

Presumably the global sysctl could be shadowed as read only, but still
some scripts expecting them being rw would break anyway.


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html