selftests: nft_concat_range: Add test for reported add/flush/add issue
authorStefano Brivio <sbrivio@redhat.com>
Fri, 21 Feb 2020 02:04:22 +0000 (03:04 +0100)
committerPablo Neira Ayuso <pablo@netfilter.org>
Wed, 26 Feb 2020 13:33:09 +0000 (14:33 +0100)
commit0954df70fba743d8cdaa09ccf6ba8e4ad09628de
tree90a12c252dd66279acf91c41e23d49dc5d2ae31c
parent212d58c106fd0f2704664be2bb173e14cb4e86d3
selftests: nft_concat_range: Add test for reported add/flush/add issue

Add a specific test for the crash reported by Phil Sutter and addressed
in the previous patch. The test cases that, in my intention, should
have covered these cases, that is, the ones from the 'concurrency'
section, don't run these sequences tightly enough and spectacularly
failed to catch this.

While at it, define a convenient way to add these kind of tests, by
adding a "reported issues" test section.

It's more convenient, for this particular test, to execute the set
setup in its own function. However, future test cases like this one
might need to call setup functions, and will typically need no tools
other than nft, so allow for this in check_tools().

The original form of the reproducer used here was provided by Phil.

Reported-by: Phil Sutter <phil@nwl.cc>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
tools/testing/selftests/netfilter/nft_concat_range.sh