lkml.org 
[lkml]   [2016]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.* with defaults
From
Date
Le 24/02/2016 23:05, Eric W. Biederman a écrit :
[snip]
> 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.
+1

> 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.
+1

\
 
 \ /
  Last update: 2016-02-25 16:01    [W:0.745 / U:0.264 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site