Commit 4962fa10 authored Jul 30, 2015 by Daniel Borkmann Committed by David S. Miller Jul 30, 2015

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>

parent ce7fa78c

lib/test_bpf.c

+2 −0

Original line number	Diff line number	Diff line
		@@ -4613,6 +4613,8 @@ static struct bpf_prog generate_filter(int which, int err)
		}

		fp->len = flen;
		/* Type doesn't really matter here as long as it's not unspec. */
		fp->type = BPF_PROG_TYPE_SOCKET_FILTER;
		memcpy(fp->insnsi, fptr, fp->len * sizeof(struct bpf_insn));

		bpf_prog_select_runtime(fp);