From: Stephen Hemminger <stephen@networkplumber.org>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Yue.Tao@windriver.com, alexandre.dietsch@windriver.com,
davem@davemloft.net, honkiko@gmail.com, cwang@twopensource.com,
Zhu Yanjun <Yanjun.Zhu@windriver.com>
Subject: Re: [PATCH V2 0/1] ipv4: net namespace does not inherit network configurations
Date: Wed, 20 Aug 2014 20:18:43 -0700 [thread overview]
Message-ID: <20140820201843.083a45d9@uryu.home.lan> (raw)
In-Reply-To: <1408588321-13537-1-git-send-email-Yanjun.Zhu@windriver.com>
On Thu, 21 Aug 2014 10:32:00 +0800
Zhu Yanjun <zyjzyj2000@gmail.com> wrote:
> V2: Following the advice from Cong Wang, I submit a patch as normal.
>
> Hi,all
>
> I did a test on kernel3.16 rc6:
>
> root@qemu1:~# echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
> root@qemu1:~# echo 1 > /proc/sys/net/ipv4/conf/all/forwarding
> root@qemu1:~# ip netns list
> root@qemu1:~# ip netns add fib1
> root@qemu1:~# ip netns exec fib1 bash
> root@qemu1:~# cat /proc/sys/net/ipv6/conf/all/forwarding
> 0
> root@qemu1:~# cat /proc/sys/net/ipv4/conf/all/forwarding
> 1
>
> The behavior of ipv4 and ipv6 is very inconsistent. I checked
> the kernel source code. I found that from this patch
> [ipv6: fix bad free of addrconf_init_net], the above difference
> appeared.
>
> Since a net namespace is independent to another. That is, there
> is no any relationship between the net namespaces. So the behavior
> of ipv4 is not correct.
>
> Based on this patch [ipv6: fix bad free of addrconf_init_net], I made
> a new patch to fix this problem on ipv4.
>
> Any reply is appreciated.
>
> Zhu Yanjun (1):
> ipv4: net namespace does not inherit network configurations
>
> net/ipv4/devinet.c | 29 ++++++++++++-----------------
> 1 file changed, 12 insertions(+), 17 deletions(-)
>
This a semantic change to network namespaces and therefore is
likely to break existing applications using network namespaces.
prev parent reply other threads:[~2014-08-21 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 2:32 [PATCH V2 0/1] ipv4: net namespace does not inherit network configurations Zhu Yanjun
2014-08-21 2:32 ` [PATCH 1/1] " Zhu Yanjun
2014-08-21 3:18 ` Stephen Hemminger [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=20140820201843.083a45d9@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=Yanjun.Zhu@windriver.com \
--cc=Yue.Tao@windriver.com \
--cc=alexandre.dietsch@windriver.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=honkiko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zyjzyj2000@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).