[PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.* with defaults

Nicolas Dichtel nicolas.dichtel at 6wind.com
Thu Feb 25 14:20:48 UTC 2016

Le 24/02/2016 23:05, Eric W. Biederman a écrit :
> In the general case the current behavior is random and not something
> applications can count on, and we would do well to fix it so it is less
> random.  In particular consider the case of an application in a
> non-initial network namespace creating a new network namespace.  It is
> not even possible to predict what values they will get for sysctls
> today.

>  From a backwards compatibility standpoint we are probably better off
> with copying from the current network namespace rather than the initial
> network namespace.  As that more closely resembles the common case
> today.

More information about the Containers mailing list