netdev - Re: [PATCH net-next] net: do not create fallback tunnels for non-default namespaces

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: <20180309120636.429d8796@redhat.com>
Date:   Fri, 9 Mar 2018 12:06:36 +0100
From:   Jiri Benc <jbenc@...hat.com>
To:     Eric Dumazet <edumazet@...gle.com>
Cc:     "David S . Miller" <davem@...emloft.net>,
        netdev <netdev@...r.kernel.org>,
        Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [PATCH net-next] net: do not create fallback tunnels for
 non-default namespaces

On Thu,  8 Mar 2018 12:51:41 -0800, Eric Dumazet wrote:
> Note that these tunnels are still created for the initial namespace,
> to be the least intrusive for typical setups.

Since this is a knob and must be turned on explicitly, why we don't get
rid of the automatic interfaces even for the initial name space? It
causes only problems nowadays, such as

ip link add name gre0 type gre <tunnel_options...>

failing with "File exists" even if there was no gre0 interface before.
And of course, even with the error, the interface with the name "gre0"
appears in the system. And of course, it does not have any of the
options specified. This is highly confusing. Not to mention the
autocreated gre0 interface is basically useless.

I'd like to switch the knob on by default on my systems and have the
kernel behave sane, finally, even without name spaces.

Thanks!

 Jiri