All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: xiyou.wangcong@gmail.com
Cc: netdev@vger.kernel.org, Yanjun.Zhu@windriver.com,
	xiangxia.m.yue@gmail.com, nicolas.dichtel@6wind.com
Subject: Re: [Patch net-next] net: introduce a knob to control whether to inherit devconf config
Date: Tue, 22 Jan 2019 11:07:39 -0800 (PST)	[thread overview]
Message-ID: <20190122.110739.525639247784135260.davem@davemloft.net> (raw)
In-Reply-To: <20190118072711.491-1-xiyou.wangcong@gmail.com>

From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Thu, 17 Jan 2019 23:27:11 -0800

> There have been many people complaining about the inconsistent
> behaviors of IPv4 and IPv6 devconf when creating new network
> namespaces.  Currently, for IPv4, we inherit all current settings
> from init_net, but for IPv6 we reset all setting to default.
> 
> This patch introduces a new /proc file
> /proc/sys/net/core/devconf_inherit_init_net to control the
> behavior of whether to inhert sysctl current settings from init_net.
> This file itself is only available in init_net.
 ...
> Reported-by: Zhu Yanjun <Yanjun.Zhu@windriver.com>
> Reported-by: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>

Applied, thanks.

      parent reply	other threads:[~2019-01-22 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  7:27 [Patch net-next] net: introduce a knob to control whether to inherit devconf config Cong Wang
2019-01-18  8:25 ` Nicolas Dichtel
2019-01-18 14:38   ` Tonghao Zhang
2019-01-22 19:07 ` David Miller [this message]

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=20190122.110739.525639247784135260.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Yanjun.Zhu@windriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=xiangxia.m.yue@gmail.com \
    --cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.