diff options
author | zhangliping <zhangliping02@baidu.com> | 2017-11-25 22:02:12 +0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-11-26 18:34:59 -0500 |
commit | 67c8d22a73128ff910e2287567132530abcf5b71 (patch) | |
tree | 11d819a00f47058e085321dceab9eb386f858882 /Documentation/sysctl | |
parent | 2734166e89639c973c6e125ac8bcfc2d9db72b70 (diff) | |
download | lwn-67c8d22a73128ff910e2287567132530abcf5b71.tar.gz lwn-67c8d22a73128ff910e2287567132530abcf5b71.zip |
openvswitch: fix the incorrect flow action alloc size
If we want to add a datapath flow, which has more than 500 vxlan outputs'
action, we will get the following error reports:
openvswitch: netlink: Flow action size 32832 bytes exceeds max
openvswitch: netlink: Flow action size 32832 bytes exceeds max
openvswitch: netlink: Actions may not be safe on all matching packets
... ...
It seems that we can simply enlarge the MAX_ACTIONS_BUFSIZE to fix it, but
this is not the root cause. For example, for a vxlan output action, we need
about 60 bytes for the nlattr, but after it is converted to the flow
action, it only occupies 24 bytes. This means that we can still support
more than 1000 vxlan output actions for a single datapath flow under the
the current 32k max limitation.
So even if the nla_len(attr) is larger than MAX_ACTIONS_BUFSIZE, we
shouldn't report EINVAL and keep it move on, as the judgement can be
done by the reserve_sfa_size.
Signed-off-by: zhangliping <zhangliping02@baidu.com>
Acked-by: Pravin B Shelar <pshelar@ovn.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/sysctl')
0 files changed, 0 insertions, 0 deletions