netdev - Re: [PATCH RFC net-next] net: Allow name change of IFF

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 11 Aug 2017 11:01:32 +0200
From:   Vitaly Kuznetsov <vkuznets@...hat.com>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     David Ahern <dsahern@...il.com>,
        David Miller <davem@...emloft.net>, andrew@...n.ch,
        eric.dumazet@...il.com, netdev@...r.kernel.org, edumazet@...gle.com
Subject: Re: [PATCH RFC net-next] net: Allow name change of IFF_UP interfaces

Stephen Hemminger <stephen@...workplumber.org> writes:

> On Thu, 10 Aug 2017 10:55:01 -0600
> David Ahern <dsahern@...il.com> wrote:
>
>> On 8/10/17 10:48 AM, David Miller wrote:
>> > From: Andrew Lunn <andrew@...n.ch>
>> > Date: Thu, 10 Aug 2017 18:27:22 +0200
>> >   
>> >> On Thu, Aug 10, 2017 at 05:24:55PM +0200, Vitaly Kuznetsov wrote:  
>> >>> Andrew Lunn <andrew@...n.ch> writes:
>> >>>  
>> >>>>> We are - rtnetlink_event() does the job. We, however, don't have a
>> >>>>> special IFLA_EVENT_* for name change and end up with IFLA_EVENT_NONE.  
>> >>>>
>> >>>> What is in this event? Old and new name? Just the new name?  
>> >>>
>> >>> Basically, it's everything we know about the interface - type, index,
>> >>> name, mtu, qdisc, ... - see rtnl_fill_ifinfo(). Back to your question -
>> >>> it's only the new name.  
>> >>
>> >> So the program needs to keep track of ifindex to know which interface
>> >> has changed name. Doable.
>> >>
>> >> I still expect this has the potential to break something. You probably
>> >> should be asking on linux-api for the API experts opinion.  
>> > 
>> > But a greater point is that nobody is monitoring device renames
>> > explicitly right now.  
>> 
>> Just to throw in an example:
>>   https://github.com/kobolabs/dhcpcd/blob/kobo/if-linux.c#L761
>> 
>> Learned of its use from a recent regression:
>> https://bugzilla.kernel.org/show_bug.cgi?id=196355
>
> Quagga is another example of what might break. Especially with all the new
> forks..

I see,

even if we don't see right away why the limitation was imposed and who
depends on this 'UP interfaces keep their names' semantics it may not be
worth it to open this pandora box just because of the netvsc driver
change...

-- 
  Vitaly