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: <20200609.123858.466960203090925019.davem@davemloft.net>
Date:   Tue, 09 Jun 2020 12:38:58 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dan.j.williams@...el.com
Cc:     stephen@...workplumber.org, corbet@....net, andrew@...n.ch,
        amitc@...lanox.com, david@...tonic.nl, linville@...driver.com,
        marex@...x.de, linux-kernel@...r.kernel.org, linux@...linux.org.uk,
        petrm@...lanox.com, hkallweit1@...il.com, kernel@...gutronix.de,
        christian.herber@....com, mkubecek@...e.cz, kuba@...nel.org,
        o.rempel@...gutronix.de, netdev@...r.kernel.org,
        mkl@...gutronix.de, f.fainelli@...il.com
Subject: Re: [PATCH ethtool v1] netlink: add master/slave configuration
 support

From: "Williams, Dan J" <dan.j.williams@...el.com>
Date: Tue, 9 Jun 2020 19:30:50 +0000

> On Tue, 2020-06-09 at 11:36 -0700, David Miller wrote:
>> From: Stephen Hemminger <stephen@...workplumber.org>
>> Date: Tue, 9 Jun 2020 10:19:35 -0700
>> 
>> > Yes, words do matter and convey a lot of implied connotation and
>> > meaning.
>> 
>> What is your long term plan?  Will you change all of the UAPI for
>> bonding for example?
> 
> The long term plan in my view includes talking with standards bodies to
> move new content to, for example, master/subordinate. In other words,
> practical forward steps, not retroactively changing interfaces.

When that knowledge is established legitimately in standards and
transferred into common knowledge of these technologies, yes then
please come present your proposals.

But right now using different words will create confusion.

I also find master/subordinate an interesting proposal, what if master
is a triggering term?  Why only slave?

I know people feel something needs to change, but do that moving
forward for the technologies themselves.  Not how we implement support
for a technology which is established already.

Plant the seed, don't chop the tree down.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ