netdev - Re: [PATCH net-next] team: Use extack to report enslavement failures

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]

Date:   Wed, 28 Feb 2018 10:29:07 +0100
From:   Jiri Pirko <jiri@...nulli.us>
To:     Jiri Benc <jbenc@...hat.com>
Cc:     Jakub Kicinski <kubakici@...pl>, Ido Schimmel <idosch@...sch.org>,
        Ido Schimmel <idosch@...lanox.com>, netdev@...r.kernel.org,
        davem@...emloft.net, jiri@...lanox.com, dsahern@...il.com,
        mlxsw@...lanox.com
Subject: Re: [PATCH net-next] team: Use extack to report enslavement failures

Wed, Feb 28, 2018 at 09:58:03AM CET, jbenc@...hat.com wrote:
>On Wed, 28 Feb 2018 08:12:41 +0100, Jiri Pirko wrote:
>> Yeah, or if you have an older iproute2 package. I would keep the existing
>> dmesg msgs for now. In the future, when everyone is used to exacks, then
>> we can remove them.
>
>How do we ensure that this will actually happen in the future? Usually,
>when not done right away, such things tend to be forgotten for years or
>even forever.
>
>Also, how distant future are we talking about?

I would say, quite distant :)
On the other hand, I don't care much about this in particular.