diff options
| author |   Alexei Starovoitov <ast@kernel.org> | 2019-11-22 10:29:38 -0800 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2019-11-24 16:58:46 -0800 |
| commit | 161f3cbcda06aa70faed6b703066fedbd7653e23 (patch) | |
| tree | dc410e35bdb263512e095f64aed2456b19e132d8 /tools/testing/selftests/bpf/progs/test_overhead.c | |
| parent | selftests/bpf: Ensure core_reloc_kernel is reading test_progs's data only (diff) | |
| parent | selftests/bpf: Add verifier tests for better jmp32 register bounds (diff) | |
| download | linux-dev-161f3cbcda06aa70faed6b703066fedbd7653e23.tar.xz linux-dev-161f3cbcda06aa70faed6b703066fedbd7653e23.zip | |
Merge branch 'jmp32-reg-bounds'
Yonghong Song says:
====================
With latest llvm, bpf selftest test_progs, which has +alu32 enabled, failed for
strobemeta.o and a few other subtests. The reason is due to that
verifier did not provide better var_off.mask after jmp32 instructions.
This patch set addressed this issue and after the fix, test_progs passed
with alu32.
Patch #1 provided detailed explanation of the problem and the fix.
Patch #2 added three tests in test_verifier.
Changelog:
v1 -> v2:
- do not directly manipulate tnum.{value,mask} in __reg_bound_offset32(),
using tnum_lshift/tnum_rshift functions instead
- do __reg_bound_offset32() after regular 64bit __reg_bound_offset()
since the latter may give a better upper 32bit var_off, which can
be inherited by __reg_bound_offset32().
====================
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions