bpf: Add BPF_F_ANY_ALIGNMENT.
Often we want to write tests cases that check things like bad context offset accesses. And one way to do this is to use an odd offset on, for example, a 32-bit load. This unfortunately triggers the alignment checks first on platforms that do not set CONFIG_EFFICIENT_UNALIGNED_ACCESS. So the test case see the alignment failure rather than what it was testing for. It is often not completely possible to respect the original intention of the test, or even test the same exact thing, while solving the alignment issue. Another option could have been to check the alignment after the context and other validations are performed by the verifier, but that is a non-trivial change to the verifier. Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
This commit is contained in:

committed by
Alexei Starovoitov

parent
88945f4606
commit
e9ee9efc0d
@@ -14275,7 +14275,8 @@ static void do_test_single(struct bpf_test *test, bool unpriv,
|
||||
prog_len = probe_filter_length(prog);
|
||||
|
||||
fd_prog = bpf_verify_program(prog_type, prog, prog_len,
|
||||
test->flags & F_LOAD_WITH_STRICT_ALIGNMENT,
|
||||
test->flags & F_LOAD_WITH_STRICT_ALIGNMENT ?
|
||||
BPF_F_STRICT_ALIGNMENT : 0,
|
||||
"GPL", 0, bpf_vlog, sizeof(bpf_vlog), 1);
|
||||
|
||||
expected_ret = unpriv && test->result_unpriv != UNDEF ?
|
||||
|
Reference in New Issue
Block a user