On Tue, Feb 22, 2022 at 12:51 PM Stijn Tintel <stijn@xxxxxxxxxxxxx> wrote: > > When a BPF map of type BPF_MAP_TYPE_PERF_EVENT_ARRAY doesn't have the > max_entries parameter set, this parameter will be set to the number of > possible CPUs. Due to this, the map_is_reuse_compat function will return > false, causing the following error when trying to reuse the map: > > libbpf: couldn't reuse pinned map at '/sys/fs/bpf/m_logging': parameter mismatch > > Fix this by checking against the number of possible CPUs if the > max_entries parameter is not set in the map definition. > > Fixes: 57a00f41644f ("libbpf: Add auto-pinning of maps when loading BPF objects") > Signed-off-by: Stijn Tintel <stijn@xxxxxxxxxxxxx> Acked-by: Song Liu <songliubraving@xxxxxx> I think the following fix would be more future proof, but the patch as-is is better for stable backport? How about we add a follow up patch on top of current patch to fix def->max_entries once for all? Thanks, Song diff --git i/tools/lib/bpf/libbpf.c w/tools/lib/bpf/libbpf.c index ad43b6ce825e..a1bc1c80bc69 100644 --- i/tools/lib/bpf/libbpf.c +++ w/tools/lib/bpf/libbpf.c @@ -4881,10 +4881,9 @@ static int bpf_object__create_map(struct bpf_object *obj, struct bpf_map *map, b return nr_cpus; } pr_debug("map '%s': setting size to %d\n", map->name, nr_cpus); - max_entries = nr_cpus; - } else { - max_entries = def->max_entries; + def->max_entries = nr_cpus; } + max_entries = def->max_entries; if (bpf_map__is_struct_ops(map)) create_attr.btf_vmlinux_value_type_id = map->btf_vmlinux_value_type_id;