diff options
author | Andrii Nakryiko <andrii@kernel.org> | 2023-11-02 19:47:41 +0300 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2023-11-10 06:06:23 +0300 |
commit | e3499962d836af085a621f005978fee20fc87276 (patch) | |
tree | 989e0be5c06e56cf68317fbd3614ed9e2423d5b2 /tools/testing/selftests/bpf/vmtest.sh | |
parent | cd9c127069c040d6b022f1ff32fed4b52b9a4017 (diff) | |
parent | 2f553b032cad4993969cab356b3b0e306fcd1cd1 (diff) | |
download | linux-e3499962d836af085a621f005978fee20fc87276.tar.xz |
Merge branch 'selftests/bpf: Fixes for map_percpu_stats test'
Hou Tao says:
====================
From: Hou Tao <houtao1@huawei.com>
Hi,
BPF CI failed due to map_percpu_stats_percpu_hash from time to time [1].
It seems that the failure reason is per-cpu bpf memory allocator may not
be able to allocate per-cpu pointer successfully and it can not refill
free llist timely, and bpf_map_update_elem() will return -ENOMEM.
Patch #1 fixes the size of value passed to per-cpu map update API. The
problem was found when fixing the ENOMEM problem, so also post it in
this patchset. Patch #2 & #3 mitigates the ENOMEM problem by retrying
the update operation for non-preallocated per-cpu map.
Please see individual patches for more details. And comments are always
welcome.
Regards,
Tao
[1]: https://github.com/kernel-patches/bpf/actions/runs/6713177520/job/18244865326?pr=5909
====================
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/testing/selftests/bpf/vmtest.sh')
0 files changed, 0 insertions, 0 deletions