netdev - Re: [PATCH net-next] of: add optional naming of interfaces

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

Message-ID: <626a2f04-6fc0-f04e-671c-4fd1e90db344@gmail.com>
Date:   Wed, 7 Dec 2016 09:49:46 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Volodymyr Bendiuga <volodymyr.bendiuga@...termo.se>,
        robh+dt@...nel.org, mark.rutland@....com, frowand.list@...il.com,
        netdev@...r.kernel.org, devicetree@...r.kernel.org,
        volodymyr.bendiuga@...il.com
Cc:     Jonas Johansson <jonas.johansson@...termo.se>,
        Mattias Walström <lazzer@...il.com>
Subject: Re: [PATCH net-next] of: add optional naming of interfaces

On 12/07/2016 05:12 AM, Volodymyr Bendiuga wrote:
> From: Jonas Johansson <jonas.johansson@...termo.se>
> 
> Signed-off-by: Mattias Walström <lazzer@...il.com>
> Signed-off-by: Jonas Johansson <jonas.johansson@...termo.se>

This does not belong to the Device Tree, there should be plenty of
information in user-space to make an educated device rename. I
definitively understand that some drivers (e.g: dsa) do actually get
their interface name from Device Tree directly (label property), but
this is probably the one and only case where this may be tolerated.

Besides, if you submit such a change, you would want to also provide a
consumer of that API to illustrate how this is used.
-- 
Florian