From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760838AbcBYQnr (ORCPT ); Thu, 25 Feb 2016 11:43:47 -0500 Received: from shards.monkeyblade.net ([149.20.54.216]:42710 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759877AbcBYQnq convert rfc822-to-8bit (ORCPT ); Thu, 25 Feb 2016 11:43:46 -0500 Date: Thu, 25 Feb 2016 11:43:43 -0500 (EST) Message-Id: <20160225.114343.1977846344387184355.davem@davemloft.net> To: nicolas.dichtel@6wind.com Cc: ebiederm@xmission.com, 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 From: David Miller In-Reply-To: <56CF0DC0.7030003@6wind.com> References: <20160223.182121.2101846699151527296.davem@davemloft.net> <87y4a9ix2h.fsf@x220.int.ebiederm.org> <56CF0DC0.7030003@6wind.com> X-Mailer: Mew version 6.6 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 25 Feb 2016 08:43:45 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Nicolas Dichtel Date: Thu, 25 Feb 2016 15:20:48 +0100 > 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 But there is a counter argument to this. The admin set up the initial namespace so that any namespace instantiated by a user (even non-initial namespaces) starts with a specific set of sysctl values. So the admin "knows", he set it up intentionally this way, and it's a valid model. This behavior is anything but random. Rather, it is very predictable and controllable. Do you really want to find out who you're going to break out there with so many installations in the world right now? I do not.