On Mon, Jan 27, 2020 at 4:58 AM Jakub Sitnicki <jakub@xxxxxxxxxxxxxx> wrote: > > Now that SOCKMAP can store listening sockets, user-space and BPF API is > open to a new set of potential pitfalls. Exercise the map operations (with > extra attention to code paths susceptible to races between map ops and > socket cloning), and BPF helpers that work with SOCKMAP to gain confidence > that all works as expected. > > Signed-off-by: Jakub Sitnicki <jakub@xxxxxxxxxxxxxx> > --- > .../selftests/bpf/prog_tests/sockmap_listen.c | 1455 +++++++++++++++++ > .../selftests/bpf/progs/test_sockmap_listen.c | 77 + > 2 files changed, 1532 insertions(+) > create mode 100644 tools/testing/selftests/bpf/prog_tests/sockmap_listen.c > create mode 100644 tools/testing/selftests/bpf/progs/test_sockmap_listen.c > Hey Jakub! I'm frequently getting spurious failures for sockmap_listen selftest. We also see that in libbpf's Github CI testing as well. Do you mind taking a look? Usually it's the following kinds of error: ./test_progs:connect_accept_thread:733: accept: Resource temporarily unavailable connect_accept_thread:FAIL:733 Thanks!
