summaryrefslogtreecommitdiffstats
path: root/tests/shell/testcases/nft-f/0023priority_variable_1
diff options
context:
space:
mode:
authorŠtěpán Němec <snemec@redhat.com>2021-12-01 12:12:00 +0100
committerPhil Sutter <phil@nwl.cc>2021-12-08 13:18:11 +0100
commit7b81d9cb094ffa96ad821528cf19269dc348f617 (patch)
tree4d28c2af3edb17770a22cf3e28729b0f07d7a321 /tests/shell/testcases/nft-f/0023priority_variable_1
parent48aca2de80a7dd73f8f3a461c7f7ed47b6082766 (diff)
tests: shell: better parameters for the interval stack overflow testHEADmaster
Wider testing has shown that 128 kB stack is too low (e.g. for systems with 64 kB page size), leading to false failures in some environments. Based on results from a matrix of RHEL 8 and RHEL 9 systems across x86_64, aarch64, ppc64le and s390x architectures as well as some anecdotal testing of other Linux distros on x86_64 machines, 400 kB seems safe: the normal nft stack (which should stay constant during this test) on all tested systems doesn't exceed 200 kB (stays around 100 kB on typical systems with 4 kB page size), while always growing beyond 500 kB in the failing case (nftables before baecd1cf2685) with the increased set size. Fixes: d8ccad2a2b73 ("tests: cover baecd1cf2685 ("segtree: Fix segfault when restoring a huge interval set")") Signed-off-by: Štěpán Němec <snemec@redhat.com> Signed-off-by: Phil Sutter <phil@nwl.cc>
Diffstat (limited to 'tests/shell/testcases/nft-f/0023priority_variable_1')
0 files changed, 0 insertions, 0 deletions