Thanks! I patched the test_maps.c to maximize the locked memory, but the problem still exists. Let me try Alexei's kernel tree on "xdp" branch to see if it works or not.
My environment: Fedora 23 in VM kernel: net-next master branch commit 601009780 gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6) LLVM version 3.7.0 On Wed, Jun 22, 2016 at 10:07 AM, Alexei Starovoitov <[email protected]> wrote: > On Wed, Jun 22, 2016 at 9:52 AM, Jesper Dangaard Brouer > <[email protected]> wrote: >> On Wed, 22 Jun 2016 08:59:14 -0700 >> Alexei Starovoitov <[email protected]> wrote: >> >>> On Wed, Jun 22, 2016 at 8:54 AM, Jesper Dangaard Brouer >>> <[email protected]> wrote: >>> > On Tue, 21 Jun 2016 18:54:53 -0700 >>> > Alexei Starovoitov <[email protected]> wrote: >>> > >>> >> On Tue, Jun 21, 2016 at 11:48 AM, William Tu via iovisor-dev >>> >> <[email protected]> wrote: >>> >> > Hi, >>> >> > >>> >> > I'm running test_maps under net-next/samples/bpf/, commit >>> >> > 601009780635. The code logic all make sense but I got the assertion >>> >> > errors / coredump for some unknown reason under different compiler >>> >> > optimization flags (-O0 and -O2). The test_hashmap_sanity() works fine >>> >> > but fails at test_percpu_hashmap_sanity(). >>> >> > >>> >> > First run with normal build (which has -O2) >>> >> > [root@vm-dev bpf]# ./test_maps >>> >> > test_maps: samples/bpf/test_maps.c:137: test_percpu_hashmap_sanity: >>> >> > Assertion `bpf_lookup_elem(map_fd, &key, value) == -1 && >>> >> > (*__errno_location ()) == 2' failed. >>> > [...] >>> > >>> > Strange I get: >>> > >>> > $ sudo ./test_maps >>> > failed to create per-cpu arraymap 'Operation not permitted' >>> >>> yes. that's expected. Make sure to do 'ulimit -l unlimited' >> >> # ulimit -l unlimited >> # ./test_maps >> test_maps: OK >> >> Then it works, thanks. Maybe we could provide some better feedback from >> the test program, as this might be a common/expected behavior. > > probably the same patch as William did for sockex[12] is needed for test_maps. > bcc does it automatically. _______________________________________________ iovisor-dev mailing list [email protected] https://lists.iovisor.org/mailman/listinfo/iovisor-dev
