libbpf: Sanitise internal map names so they are not rejected by the kernel
authorToke Høiland-Jørgensen <toke@redhat.com>
Mon, 17 Feb 2020 17:17:01 +0000 (18:17 +0100)
committerDaniel Borkmann <daniel@iogearbox.net>
Tue, 18 Feb 2020 14:34:20 +0000 (15:34 +0100)
commit113e6b7e15e23dc45d5c66eb66bb91a627812e36
tree96d646cc04e8d070610f657cb716217268e2d3d9
parentf25975f42f2f8f2a01303054d6a70c7ceb1fcf54
libbpf: Sanitise internal map names so they are not rejected by the kernel

The kernel only accepts map names with alphanumeric characters, underscores
and periods in their name. However, the auto-generated internal map names
used by libbpf takes their prefix from the user-supplied BPF object name,
which has no such restriction. This can lead to "Invalid argument" errors
when trying to load a BPF program using global variables.

Fix this by sanitising the map names, replacing any non-allowed characters
with underscores.

Fixes: d859900c4c56 ("bpf, libbpf: support global data/bss/rodata sections")
Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/bpf/20200217171701.215215-1-toke@redhat.com
tools/lib/bpf/libbpf.c