David Miller 89087c456f bpf: Fix values type used in test_maps ... Maps of per-cpu type have their value element size adjusted to 8 if it is specified smaller during various map operations. This makes test_maps as a 32-bit binary fail, in fact the kernel writes past the end of the value's array on the user's stack. To be quite honest, I think the kernel should reject creation of a per-cpu map that doesn't have a value size of at least 8 if that's what the kernel is going to silently adjust to later. If the user passed something smaller, it is a sizeof() calcualtion based upon the type they will actually use (just like in this testcase code) in later calls to the map operations. Fixes: df570f5772 ("samples/bpf: unit test for BPF_MAP_TYPE_PERCPU_ARRAY") Signed-off-by: David S. Miller <davem@davemloft.net> Acked-by: Daniel Borkmann <daniel@iogearbox.net> Acked-by: Alexei Starovoitov <ast@kernel.org>		2017-04-21 15:16:46 -04:00
..
fault-injection	fault-injection: fix failcmd.sh warning	2012-07-31 18:42:38 -07:00
ktest	Greg Kroah-Hartman reported to me that the ktest of v4.10 locked up in an	2017-03-08 11:06:05 -08:00
nvdimm	tools/testing/nvdimm: make iset cookie predictable	2017-03-01 00:09:51 -08:00
radix-tree	radix tree test suite: Specify -m32 in LDFLAGS too	2017-03-07 13:18:24 -05:00
selftests	bpf: Fix values type used in test_maps	2017-04-21 15:16:46 -04:00