diff options
author | Davide Caratti <dcaratti@redhat.com> | 2021-05-19 15:17:21 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2021-05-19 13:10:24 -0700 |
commit | 05ff8435e50569a0a6b95e5ceaea43696e8827ab (patch) | |
tree | b73493aa05464777f897edc7690e2119f8efd85a | |
parent | 7b16509b29e007d15b158aa52bea25b22faf7972 (diff) |
net/sched: cls_api: increase max_reclassify_loop
modern userspace applications, like OVN, can configure the TC datapath to
"recirculate" packets several times. If more than 4 "recirculation" rules
are configured, packets can be dropped by __tcf_classify().
Changing the maximum number of reclassifications (from 4 to 16) should be
sufficient to prevent drops in most use cases, and guard against loops at
the same time.
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
-rw-r--r-- | net/sched/cls_api.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c index 40fbea626dfd..75e3a288a7c8 100644 --- a/net/sched/cls_api.c +++ b/net/sched/cls_api.c @@ -1531,7 +1531,7 @@ static inline int __tcf_classify(struct sk_buff *skb, u32 *last_executed_chain) { #ifdef CONFIG_NET_CLS_ACT - const int max_reclassify_loop = 4; + const int max_reclassify_loop = 16; const struct tcf_proto *first_tp; int limit = 0; |