bpftool: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK
authorYafang Shao <laoar.shao@gmail.com>
Sat, 9 Apr 2022 12:59:57 +0000 (12:59 +0000)
committerAndrii Nakryiko <andrii@kernel.org>
Mon, 11 Apr 2022 03:17:16 +0000 (20:17 -0700)
commita777e18f1bcd32528ff5dfd10a6629b655b05eb8
tree681ae396647ca9e5cb2d977f135e365d4a226c12
parentb858ba8c52b64c038de156c455a39a89bfd214e8
bpftool: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK

We have switched to memcg-based memory accouting and thus the rlimit is
not needed any more. LIBBPF_STRICT_AUTO_RLIMIT_MEMLOCK was introduced in
libbpf for backward compatibility, so we can use it instead now.

libbpf_set_strict_mode always return 0, so we don't need to check whether
the return value is 0 or not.

Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/bpf/20220409125958.92629-4-laoar.shao@gmail.com
tools/bpf/bpftool/common.c
tools/bpf/bpftool/feature.c
tools/bpf/bpftool/main.c
tools/bpf/bpftool/main.h
tools/bpf/bpftool/map.c
tools/bpf/bpftool/pids.c
tools/bpf/bpftool/prog.c
tools/bpf/bpftool/struct_ops.c