netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: "Mahesh Bandewar (महेश बंडेवार)" <maheshb@google.com>
Cc: David Miller <davem@davemloft.net>,
	Mahesh Bandewar <mahesh@bandewar.net>,
	James Morris <jmorris@namei.org>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	Patrick McHardy <kaber@trash.net>,
	Eric Dumazet <edumazet@google.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/2] bring UP loopback device at initialziation
Date: Wed, 5 Jul 2017 10:48:56 -0700	[thread overview]
Message-ID: <CAM_iQpXB6NSKK8ibE_r2SqLaLTsUQicVE8LqmdQ7qAz8-+AH_Q@mail.gmail.com> (raw)
In-Reply-To: <CAF2d9jjZ0XJDo3qYKnNgeMMLQXgUwt5ga8p_cWd5x-DjhzwWyA@mail.gmail.com>

On Wed, Jul 5, 2017 at 8:59 AM, Mahesh Bandewar (महेश बंडेवार)
<maheshb@google.com> wrote:
> Systems have only one lo device (since ages) and that is usually taken
> care at the boot time. Now with the namespaces it's not just one
> device as it's per namespace and though not much this patch will
> benefit a little. Probably we should ask a question - is it going to
> have any bad effects? I couldn't find any and my RFC patch did not get
> me any such feedback. As far as the good effects are concerned, it has
> already found a bug (another patch in this series)! Also sometime back
> I did experience weird behavior inside net-namespace if you forget to
> bring-up the loopback device. I didn't pay too much attention as
> bringing up the lo device fixed it.
>

I wonder if it is too late to change this since this behavior is probably
from the beginning of network namespace. A networkless netns is also
useful at least for testing purpose, we do use it as a sandbox.

      parent reply	other threads:[~2017-07-05 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 19:16 [PATCH 0/2] bring UP loopback device at initialziation Mahesh Bandewar
2017-07-05  8:20 ` David Miller
2017-07-05 15:59   ` Mahesh Bandewar (महेश बंडेवार)
2017-07-05 16:05     ` David Miller
2017-07-05 17:50       ` Mahesh Bandewar (महेश बंडेवार)
     [not found]         ` <871spuek9i.fsf@xmission.com>
2017-07-05 23:01           ` Mahesh Bandewar (महेश बंडेवार)
2017-07-06 12:18             ` Eric W. Biederman
2017-07-06 17:48               ` Mahesh Bandewar (महेश बंडेवार)
2017-07-06 18:40             ` Cong Wang
2017-07-05 17:48     ` Cong Wang [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=CAM_iQpXB6NSKK8ibE_r2SqLaLTsUQicVE8LqmdQ7qAz8-+AH_Q@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=edumazet@google.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=mahesh@bandewar.net \
    --cc=maheshb@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.org \
    /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).