diff options
author | Daniel Borkmann <daniel@iogearbox.net> | 2015-07-30 12:42:46 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-07-30 11:13:20 -0700 |
commit | 4962fa10f30d7b563f38467feeae10314b166c77 (patch) | |
tree | f813e5296c805668bb463f7db4075343307d406f /init | |
parent | ce7fa78ce16e476a610e165dd0e8c1e85a75d60f (diff) | |
download | linux-4962fa10f30d7b563f38467feeae10314b166c77.tar.bz2 |
test_bpf: assign type to native eBPF test cases
As JITs start to perform optimizations whether to clear A and X on eBPF
programs in the prologue, we should actually assign a program type to the
native eBPF test cases. It doesn't really matter which program type, as
these instructions don't go through the verifier, but it needs to be a
type != BPF_PROG_TYPE_UNSPEC. This reflects eBPF programs loaded via bpf(2)
system call (!= type unspec) vs. classic BPF to eBPF migrations (== type
unspec).
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions