diff options
author | Paul Blakey <paulb@nvidia.com> | 2022-01-06 17:38:04 +0200 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2022-01-09 16:24:12 -0800 |
commit | 6f022c2ddbcefaee79502ce5386dfe351d457070 (patch) | |
tree | d551a30d87db083573f66dfc2756ce22c818fbed /include/net/dst.h | |
parent | f4bb93a82f94a1e23e532f0b4b1859f1f4605968 (diff) | |
download | linux-6f022c2ddbcefaee79502ce5386dfe351d457070.tar.bz2 |
net: openvswitch: Fix ct_state nat flags for conns arriving from tc
Netfilter conntrack maintains NAT flags per connection indicating
whether NAT was configured for the connection. Openvswitch maintains
NAT flags on the per packet flow key ct_state field, indicating
whether NAT was actually executed on the packet.
When a packet misses from tc to ovs the conntrack NAT flags are set.
However, NAT was not necessarily executed on the packet because the
connection's state might still be in NEW state. As such, openvswitch
wrongly assumes that NAT was executed and sets an incorrect flow key
NAT flags.
Fix this, by flagging to openvswitch which NAT was actually done in
act_ct via tc_skb_ext and tc_skb_cb to the openvswitch module, so
the packet flow key NAT flags will be correctly set.
Fixes: b57dc7c13ea9 ("net/sched: Introduce action ct")
Signed-off-by: Paul Blakey <paulb@nvidia.com>
Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
Link: https://lore.kernel.org/r/20220106153804.26451-1-paulb@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/net/dst.h')
0 files changed, 0 insertions, 0 deletions