libbpf: fix up few libbpf.map problems
authorAndrii Nakryiko <andrii@kernel.org>
Mon, 27 Jun 2022 21:15:27 +0000 (14:15 -0700)
committerAlexei Starovoitov <ast@kernel.org>
Tue, 28 Jun 2022 20:13:33 +0000 (13:13 -0700)
Seems like we missed to add 2 APIs to libbpf.map and another API was
misspelled. Fix it in libbpf.map.

Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/r/20220627211527.2245459-16-andrii@kernel.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
tools/lib/bpf/libbpf.map
tools/lib/bpf/libbpf_legacy.h

index 236efc7338f18a6f22592aa7f801ce19051b1b8f..43c6697a6d27afc9a1204dc4535b5be49929da71 100644 (file)
@@ -326,10 +326,11 @@ LIBBPF_0.7.0 {
                bpf_xdp_detach;
                bpf_xdp_query;
                bpf_xdp_query_id;
+               btf_ext__raw_data;
                libbpf_probe_bpf_helper;
                libbpf_probe_bpf_map_type;
                libbpf_probe_bpf_prog_type;
-               libbpf_set_memlock_rlim_max;
+               libbpf_set_memlock_rlim;
 } LIBBPF_0.6.0;
 
 LIBBPF_0.8.0 {
index 863f49df8bf4162f4755c32be7a95892bdafa5b9..5b7e0155db6a5a9b8358100a98172632935fb333 100644 (file)
@@ -76,8 +76,8 @@ enum libbpf_strict_mode {
         * first BPF program or map creation operation. This is done only if
         * kernel is too old to support memcg-based memory accounting for BPF
         * subsystem. By default, RLIMIT_MEMLOCK limit is set to RLIM_INFINITY,
-        * but it can be overriden with libbpf_set_memlock_rlim_max() API.
-        * Note that libbpf_set_memlock_rlim_max() needs to be called before
+        * but it can be overriden with libbpf_set_memlock_rlim() API.
+        * Note that libbpf_set_memlock_rlim() needs to be called before
         * the very first bpf_prog_load(), bpf_map_create() or bpf_object__load()
         * operation.
         */