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
| ||
|
Date: Wed, 28 Feb 2018 08:12:41 +0100 From: Jiri Pirko <jiri@...nulli.us> To: Jakub Kicinski <kubakici@...pl> Cc: Ido Schimmel <idosch@...sch.org>, Jiri Benc <jbenc@...hat.com>, 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 12:49:59AM CET, kubakici@...pl wrote: >On Tue, 27 Feb 2018 22:22:12 +0200, Ido Schimmel wrote: >> > If so, for how long? They should certainly be removed eventually. How >> > do we ensure we don't forget? >> > >> > Seems to me it would be better to remove them right now. >> >> I can do that unless someone objects. > >I don't object, but FWIW keep in mind extack errors don't show if >libmnl is not installed.. 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.
Powered by blists - more mailing lists