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: Sun, 8 Jan 2017 10:46:24 +0200 From: Amir Vadai <amir@...ai.me> To: David Miller <davem@...emloft.net> Cc: netdev@...r.kernel.org, jiri@...lanox.com, ogerlitz@...lanox.com, hadarh@...lanox.com Subject: Re: [PATCH net-next V2 0/3] net/sched: act_pedit: Use offset relative to conventional network headers On Fri, Jan 06, 2017 at 08:51:09PM -0500, David Miller wrote: > From: Amir Vadai <amir@...ai.me> > Date: Thu, 5 Jan 2017 11:54:51 +0200 > > > Enhancing the UAPI to allow for specifying that would allow the same > > flows to be set into both SW and HW. > > This is actually not backward compatible. > > When pedit rules are dumped, older tools will not know about the > type field and therefore will completely misinterpret the rule. > > You must extend this the proper way, which is to add a new attribute > or something along those lines. The presense of a new attribute > is an explicit communication to older tools that somethng they > might not support and understand is going on. Sorry, I missed this scenario. Going back to the drawing board.
Powered by blists - more mailing lists