netdev - Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master

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: <20220921153349.0519c35d@hermes.local>
Date:   Wed, 21 Sep 2022 15:33:49 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Vladimir Oltean <vladimir.oltean@....com>
Cc:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        David Ahern <dsahern@...nel.org>, Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and
 change DSA master

On Wed, 21 Sep 2022 18:38:28 +0000
Vladimir Oltean <vladimir.oltean@....com> wrote:

> On Wed, Sep 21, 2022 at 11:36:37AM -0700, Stephen Hemminger wrote:
> > On Wed, 21 Sep 2022 19:51:05 +0300
> > Vladimir Oltean <vladimir.oltean@....com> wrote:
> >   
> > > +.BI master " DEVICE"
> > > +- change the DSA master (host network interface) responsible for handling the
> > > +local traffic termination of the given DSA switch user port. The selected
> > > +interface must be eligible for operating as a DSA master of the switch tree
> > > +which the DSA user port is a part of. Eligible DSA masters are those interfaces
> > > +which have an "ethernet" reference towards their firmware node in the firmware
> > > +description of the platform, or LAG (bond, team) interfaces which contain only
> > > +such interfaces as their ports.  
> > 
> > We still need to find a better name for this.
> > DSA predates the LF inclusive naming but that doesn't mean it can't be
> > fixed in user visible commands.  
> 
> Need? Why need? Who needs this and since when?

There is no reason that words with long emotional history need to be used
in network command.

https://inclusivenaming.org/word-lists/

https://inclusivenaming.org/word-lists/tier-1/

I understand that you and others that live in different geographies may
have different feelings about this. But the goal as a community to
not use names and terms that may hinder new diverse people from
being involved.