netdev - Re: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1

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] [day] [month] [year] [list]

Message-ID: <20170304094321.GA1753@nanopsycho>
Date:   Sat, 4 Mar 2017 10:43:22 +0100
From:   Jiri Pirko <jiri@...nulli.us>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     Nicolas Dichtel <nicolas.dichtel@...nd.com>,
        Dan Geist <dan@...ter.net>,
        Stephen Hemminger <stephen@...workplumber.org>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>,
        chenweilong@...wei.com, Jiri Pirko <jiri@...lanox.com>
Subject: Re: [Bug 194749] New: kernel bonding does not work in a network
 nameservice in versions above 3.10.0-229.20.1

Fri, Mar 03, 2017 at 07:11:32PM CET, xiyou.wangcong@...il.com wrote:
>On Fri, Mar 3, 2017 at 8:03 AM, Jiri Pirko <jiri@...nulli.us> wrote:
>> If that use case exists I believe it is an abuse. Soft devices that are
>> by definition in upper-lower relationships with other devices should not
>> move to other namespaces. Prevents all kinds of issues. If you need a
>> soft device like bridge of bond within a namespace, just create it there.
>>
>
>I can't agree. Dan's use case is pretty valid, lower devices are moved
>into a netns before enslaving to the bonding device, it is perfect valid.

I'm not saying it isn't...


>NETIF_F_NETNS_LOCAL was introduced for loopback which is
>created during netns creation, forcing users to create a bond device in
>each netns is not friendly.
>
>What issues are you talking about there? Can't we just fix them?