linux-kernel - Re: [PATCH net-next 2/5] bonding: rename slave to link where possible

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: <20200922.165114.402110655616716896.davem@davemloft.net>
Date:   Tue, 22 Sep 2020 16:51:14 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     mkubecek@...e.cz
Cc:     jarod@...hat.com, linux-kernel@...r.kernel.org,
        j.vosburgh@...il.com, vfalico@...il.com, andy@...yhouse.net,
        kuba@...nel.org, tadavis@....gov, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 2/5] bonding: rename slave to link where
 possible

From: Michal Kubecek <mkubecek@...e.cz>
Date: Wed, 23 Sep 2020 01:23:17 +0200

> Even if the module parameters are deprecated and extremely inconvenient
> as a mean of bonding configuration, I would say changing their names
> would still count as "breaking the userspace".

I totally agree.

Anything user facing has to be kept around for the deprecation period,
and that includes module parameters.