Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1338871 > unrolled thread

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

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.*  with defaults Konstantin Khlebnikov <khlebnikov@yandex-team.ru> - 2016-02-21 18:40 +0100

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

On 21.02.2016 12:25, Vasily Averin wrote:
> Konstantin,
> I've investigated question with sysctls initialization inside namespaces some time ago.
> IIRC I've found people expect that sysctl values should be inherited from parent namespace.
> It allows node admin to adjust unsafe pre-compiled settings, and prepare adequate defaults
> before creation of namespaces.

Only few sysctls are handled in this manner and they are copied from host,
not parent. This works somehow for flat containers, as soon as you go deeper
this turns into madness. Default settings must be controlled by software who
creates namespaces. For now it must reset all yet-not-known sysctls into sane defaults.

BTW two ipv6 sysctl are special: net.ipv6.conf.default.disable_ipv6 and
net.ipv6.conf.default.autoconf their defaults are controlled by module
parameters and inherited by all namespaces. And this makes sense.

>
> However, there is corner case:
> module with sysctl can be loaded after creation of namespaces.
> In this case namespaces will get pre-compiled sysctl defaults,
> and are not be able to adjust them even if they want to do it.
>
> Thank you,
> 	Vasily Averin
>
> On 21.02.2016 10:11, Konstantin Khlebnikov wrote:
>> Currently initial net.ipv4.conf.all.* and net.ipv4.conf.default.* are
>> copied from init network namespace because static structures are used
>> for init_net. This makes no sense because new netns might be created
>> from any netns. This patch makes private copy also for init netns if
>> network namespaces are enabled. Other sysctls in net.ipv4 and net.ipv6
>> already initialized with default values at namespace creation.
>>
>> Signed-off-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
>> Fixes: 752d14dc6aa9 ("[IPV4]: Move the devinet pointers on the struct net")
>> ---
>>   net/ipv4/devinet.c |    2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
>> index cebd9d31e65a..9d73d4bbdba3 100644
>> --- a/net/ipv4/devinet.c
>> +++ b/net/ipv4/devinet.c
>> @@ -2290,7 +2290,7 @@ static __net_init int devinet_init_net(struct net *net)
>>   	all = &ipv4_devconf;
>>   	dflt = &ipv4_devconf_dflt;
>>
>> -	if (!net_eq(net, &init_net)) {
>> +	if (IS_ENABLED(CONFIG_NET_NS)) {
>>   		all = kmemdup(all, sizeof(ipv4_devconf), GFP_KERNEL);
>>   		if (!all)
>>   			goto err_alloc_all;
>>
>>


-- 
Konstantin

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web