summaryrefslogtreecommitdiffstats
path: root/vpp-api-test/vat/api_format.c
diff options
context:
space:
mode:
authorAlex Popovsky <apopovsk@cisco.com>2016-09-01 20:57:45 -0700
committerJohn Lo <loj@cisco.com>2016-09-02 10:46:15 +0000
commit52901246e02c3d648c25a089c3dce5b6b4fb3112 (patch)
treea9a121a0a5a62f0bac73991c884ee4741c62a346 /vpp-api-test/vat/api_format.c
parentee4743adf5019ccc800257991492aec75d2f3e44 (diff)
Fix for invalid check of SPARSE_VEC_INVALID_INDEX
When looking up a UDP port / GRE protocol in the sparse vectors next_by_dst_port / next_by_protocol a data from the vector was tested for SPARSE_VEC_INVALID_INDEX instead of sparse index itself. This doesn’t matter for most cases since V[0] = 0 is true for all sparse vectors. This however could cause an issue when a valid sparse entry e.g. V[1234] = 0, with data (0) mistakenly passing the test for SPARSE_VEC_INVALID_INDEX, while the index itself (1234) is a valid index. Change-Id: I04818cc43efeae047a4dae79078157d48b8c359c Signed-off-by: Alex Popovsky <apopovsk@cisco.com>
Diffstat (limited to 'vpp-api-test/vat/api_format.c')
0 files changed, 0 insertions, 0 deletions