diff options
author | Xin Long <lucien.xin@gmail.com> | 2025-03-08 21:05:43 +0300 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2025-03-13 12:29:34 +0300 |
commit | 1063ae07383c0ddc5bcce170260c143825846b03 (patch) | |
tree | 192b2bc6b08b4202707d6d322b9ca20721cfe2f2 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
parent | a1e64addf3ff9257b45b78bc7d743781c3f41340 (diff) | |
download | linux-1063ae07383c0ddc5bcce170260c143825846b03.tar.xz |
Revert "openvswitch: switch to per-action label counting in conntrack"
Currently, ovs_ct_set_labels() is only called for confirmed conntrack
entries (ct) within ovs_ct_commit(). However, if the conntrack entry
does not have the labels_ext extension, attempting to allocate it in
ovs_ct_get_conn_labels() for a confirmed entry triggers a warning in
nf_ct_ext_add():
WARN_ON(nf_ct_is_confirmed(ct));
This happens when the conntrack entry is created externally before OVS
increments net->ct.labels_used. The issue has become more likely since
commit fcb1aa5163b1 ("openvswitch: switch to per-action label counting
in conntrack"), which changed to use per-action label counting and
increment net->ct.labels_used when a flow with ct action is added.
Since there’s no straightforward way to fully resolve this issue at the
moment, this reverts the commit to avoid breaking existing use cases.
Fixes: fcb1aa5163b1 ("openvswitch: switch to per-action label counting in conntrack")
Reported-by: Jianbo Liu <jianbol@nvidia.com>
Signed-off-by: Xin Long <lucien.xin@gmail.com>
Acked-by: Aaron Conole <aconole@redhat.com>
Link: https://patch.msgid.link/1bdeb2f3a812bca016a225d3de714427b2cd4772.1741457143.git.lucien.xin@gmail.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions