diff options
| author |   Stanislav Fomichev <sdf@google.com> | 2019-01-16 14:03:17 -0800 |
|---|---|---|
| committer |   Daniel Borkmann <daniel@iogearbox.net> | 2019-01-17 16:43:18 +0100 |
| commit | f67ad87ab3120e82845521b18a2b99273a340308 (patch) | |
| tree | 051b55414a98c357d5e0e948f8fc9d55e3acd095 /kernel | |
| parent | bpf: zero out build_id for BPF_STACK_BUILD_ID_IP (diff) | |
| download | wireguard-linux-f67ad87ab3120e82845521b18a2b99273a340308.tar.xz wireguard-linux-f67ad87ab3120e82845521b18a2b99273a340308.zip | |
selftests/bpf: retry tests that expect build-id
While running test_progs in a loop I found out that I'm sometimes hitting
"Didn't find expected build ID from the map" error.
Looking at stack_map_get_build_id_offset() it seems that it is racy (by
design) and can sometimes return BPF_STACK_BUILD_ID_IP (i.e. can't trylock
current->mm->mmap_sem).
Let's retry this test a single time.
Fixes: 13790d1cc72c ("bpf: add selftest for stackmap with build_id in NMI context")
Acked-by: Song Liu <songliubraving@fb.com>
Signed-off-by: Stanislav Fomichev <sdf@google.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions