5394547798
If user specifies priority=0 for some of ACL rules
that can cause rte_acl_classify to return wrong results.
The reason is that priority zero is used internally for no-match nodes.
See more details at: https://bugs.dpdk.org/show_bug.cgi?id=79.
The simplest way to overcome the issue is just not allow zero
to be a valid priority for the rule.
Fixes:
|
||
|---|---|---|
| .. | ||
| acl_bld.c | ||
| acl_gen.c | ||
| acl_run_altivec.c | ||
| acl_run_altivec.h | ||
| acl_run_avx2.c | ||
| acl_run_avx2.h | ||
| acl_run_neon.c | ||
| acl_run_neon.h | ||
| acl_run_scalar.c | ||
| acl_run_sse.c | ||
| acl_run_sse.h | ||
| acl_run.h | ||
| acl_vect.h | ||
| acl.h | ||
| Makefile | ||
| meson.build | ||
| rte_acl_osdep.h | ||
| rte_acl_version.map | ||
| rte_acl.c | ||
| rte_acl.h | ||
| tb_mem.c | ||
| tb_mem.h | ||