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


Groups > linux.kernel > #1341538

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

From Konstantin Khlebnikov <koct9i@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.* with defaults
Date 2016-02-24 06:20 +0100
Message-ID <r5A1H-87D-1@gated-at.bofh.it> (permalink)
References <r4G9d-XY-29@gated-at.bofh.it> <r5uz0-4cb-35@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Feb 24, 2016 at 2:21 AM, David Miller <davem@davemloft.net> wrote:
> From: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
> Date: Sun, 21 Feb 2016 10:11:02 +0300
>
>> 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")
>
> The horse has long left the stable on this.  We cannot change this now
> without breaking things.
>
> Imagine someone who intentionally sets up init_net with a certain set
> of settings and expects them to propagate into every created namespace.
>
> We'll break things for them and given the behavior existed for so long
> what the administrator is doing is very reasonable.
>
> I'm not applying this sorry, we are stuck with the current behavior
> whether we like it or not.

Major kernel upgrades always break something in weird setups.
This shouldn't block bug fixing.

This kludge works only for several ipv4 sysctls. If software or man ever
have tried to setup ipv6 or tune tcp and want some non-default setup then
it/he already knows that sysctls must be configured inside.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH] ipv4: in new netns initialize sysctls in  net.ipv4.conf.* with defaults David Miller <davem@davemloft.net> - 2016-02-24 00:30 +0100
  Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.*  with defaults Konstantin Khlebnikov <koct9i@gmail.com> - 2016-02-24 06:20 +0100
    Re: [PATCH] ipv4: in new netns initialize sysctls in  net.ipv4.conf.* with defaults David Miller <davem@davemloft.net> - 2016-02-24 16:30 +0100
  Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.* with defaults ebiederm@xmission.com (Eric W. Biederman) - 2016-02-24 23:20 +0100
    Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.*  with defaults Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-02-25 15:30 +0100
      Re: [PATCH] ipv4: in new netns initialize sysctls in  net.ipv4.conf.* with defaults David Miller <davem@davemloft.net> - 2016-02-25 17:50 +0100

csiph-web