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
| ||
|
Message-Id: <20160313.222021.992619751926439337.davem@davemloft.net> Date: Sun, 13 Mar 2016 22:20:21 -0400 (EDT) From: David Miller <davem@...emloft.net> To: samuel.gauthier@...nd.com Cc: pshelar@...ira.com, netdev@...r.kernel.org, dev@...nvswitch.org Subject: Re: [PATCH v2 net-next] ovs: allow nl 'flow set' to use ufid without flow key From: Samuel Gauthier <samuel.gauthier@...nd.com> Date: Thu, 10 Mar 2016 17:14:59 +0100 > When we want to change a flow using netlink, we have to identify it to > be able to perform a lookup. Both the flow key and unique flow ID > (ufid) are valid identifiers, but we always have to specify the flow > key in the netlink message. When both attributes are there, the ufid > is used. The flow key is used to validate the actions provided by > the userland. > > This commit allows to use the ufid without having to provide the flow > key, as it is already done in the netlink 'flow get' and 'flow del' > path. The flow key remains mandatory when an action is provided. > > Signed-off-by: Samuel Gauthier <samuel.gauthier@...nd.com> Applied.
Powered by blists - more mailing lists