From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
David Miller <davem@davemloft.net>
Cc: khlebnikov@yandex-team.ru, netdev@vger.kernel.org,
containers@lists.linux-foundation.org, vvs@virtuozzo.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.* with defaults
Date: Thu, 25 Feb 2016 15:20:48 +0100 [thread overview]
Message-ID: <56CF0DC0.7030003@6wind.com> (raw)
In-Reply-To: <87y4a9ix2h.fsf@x220.int.ebiederm.org>
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
next prev parent reply other threads:[~2016-02-25 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 7:11 Konstantin Khlebnikov
2016-02-21 9:25 ` Vasily Averin
2016-02-21 16:58 ` Konstantin Khlebnikov
2016-02-21 22:06 ` Eric W. Biederman
2016-02-23 23:21 ` David Miller
2016-02-24 5:16 ` Konstantin Khlebnikov
2016-02-24 15:20 ` David Miller
2016-02-24 22:05 ` Eric W. Biederman
2016-02-25 14:20 ` Nicolas Dichtel [this message]
2016-02-25 16:43 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56CF0DC0.7030003@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=containers@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vvs@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome