diff options
author | Andrii Nakryiko <[email protected]> | 2023-11-11 17:06:07 -0800 |
---|---|---|
committer | Alexei Starovoitov <[email protected]> | 2023-11-15 12:03:42 -0800 |
commit | 8c5677f8b31e92b57be7d5d0fbb1ac66eedf4f91 (patch) | |
tree | 411aa72cc5b0e5744fc11a1b7dee8b7bcc2f8d21 /tools/perf/scripts/python/arm-cs-trace-disasm.py | |
parent | dab16659c50e8c9c7c5d9584beacec28c769dcca (diff) |
selftests/bpf: set BPF_F_TEST_SANITY_SCRIPT by default
Make sure to set BPF_F_TEST_SANITY_STRICT program flag by default across
most verifier tests (and a bunch of others that set custom prog flags).
There are currently two tests that do fail validation, if enforced
strictly: verifier_bounds/crossing_64_bit_signed_boundary_2 and
verifier_bounds/crossing_32_bit_signed_boundary_2. To accommodate them,
we teach test_loader a flag negation:
__flag(!<flagname>) will *clear* specified flag, allowing easy opt-out.
We apply __flag(!BPF_F_TEST_SANITY_STRICT) to these to tests.
Also sprinkle BPF_F_TEST_SANITY_STRICT everywhere where we already set
test-only BPF_F_TEST_RND_HI32 flag, for completeness.
Acked-by: Eduard Zingerman <[email protected]>
Signed-off-by: Andrii Nakryiko <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Alexei Starovoitov <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions