summaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorTony Ambardar <tony.ambardar@gmail.com>2020-08-31 02:03:04 +0200
committerDaniel Borkmann <daniel@iogearbox.net>2020-08-31 16:56:51 +0200
commit3168c158ad3535af1cd7423c9f8cd5ac549f2f9c (patch)
treed160e52df1d32b63527198ff82931620d1cecc44 /virt
parentMerge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf (diff)
downloadlinux-3168c158ad3535af1cd7423c9f8cd5ac549f2f9c.tar.xz
linux-3168c158ad3535af1cd7423c9f8cd5ac549f2f9c.zip
libbpf: Fix build failure from uninitialized variable warning
While compiling libbpf, some GCC versions (at least 8.4.0) have difficulty determining control flow and a emit warning for potentially uninitialized usage of 'map', which results in a build error if using "-Werror": In file included from libbpf.c:56: libbpf.c: In function '__bpf_object__open': libbpf_internal.h:59:2: warning: 'map' may be used uninitialized in this function [-Wmaybe-uninitialized] libbpf_print(level, "libbpf: " fmt, ##__VA_ARGS__); \ ^~~~~~~~~~~~ libbpf.c:5032:18: note: 'map' was declared here struct bpf_map *map, *targ_map; ^~~ The warning/error is false based on code inspection, so silence it with a NULL initialization. Fixes: 646f02ffdd49 ("libbpf: Add BTF-defined map-in-map support") Reference: 063e68813391 ("libbpf: Fix false uninitialized variable warning") Signed-off-by: Tony Ambardar <Tony.Ambardar@gmail.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Link: https://lore.kernel.org/bpf/20200831000304.1696435-1-Tony.Ambardar@gmail.com
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions