netdev - Re: [PATCH 0/2] bring UP loopback device at initialziation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAM_iQpXB6NSKK8ibE_r2SqLaLTsUQicVE8LqmdQ7qAz8-+AH_Q@mail.gmail.com>
Date:   Wed, 5 Jul 2017 10:48:56 -0700
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     Mahesh Bandewar (महेश बंडेवार) 
        <maheshb@...gle.com>
Cc:     David Miller <davem@...emloft.net>,
        Mahesh Bandewar <mahesh@...dewar.net>,
        James Morris <jmorris@...ei.org>,
        Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
        Patrick McHardy <kaber@...sh.net>,
        Eric Dumazet <edumazet@...gle.com>,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        linux-netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 0/2] bring UP loopback device at initialziation

On Wed, Jul 5, 2017 at 8:59 AM, Mahesh Bandewar (महेश बंडेवार)
<maheshb@...gle.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.