Andreas Ziegler cedc12c5b5 libbpf: Add NULL checks to bpf_object__{prev_map,next_map} ... In the current state, an erroneous call to bpf_object__find_map_by_name(NULL, ...) leads to a segmentation fault through the following call chain: bpf_object__find_map_by_name(obj = NULL, ...) -> bpf_object__for_each_map(pos, obj = NULL) -> bpf_object__next_map((obj = NULL), NULL) -> return (obj = NULL)->maps While calling bpf_object__find_map_by_name with obj = NULL is obviously incorrect, this should not lead to a segmentation fault but rather be handled gracefully. As __bpf_map__iter already handles this situation correctly, we can delegate the check for the regular case there and only add a check in case the prev or next parameter is NULL. Signed-off-by: Andreas Ziegler <ziegler.andreas@siemens.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Link: https://lore.kernel.org/bpf/20240703083436.505124-1-ziegler.andreas@siemens.com		2024-07-08 18:13:07 +02:00
..
api	tools api fs: Avoid reading whole file for a 1 byte bool	2023-11-30 19:25:19 -03:00
bpf	libbpf: Add NULL checks to bpf_object__{prev_map,next_map}	2024-07-08 18:13:07 +02:00
perf	perf record: Fix comment misspellings	2024-04-26 22:13:10 -03:00
subcmd	tools lib subcmd: Show parent options in help	2024-05-12 21:09:52 -03:00
symbol
thermal
argv_split.c
bitmap.c
ctype.c
find_bit.c
hweight.c
list_sort.c
rbtree.c	tools lib rbtree: pick some improvements from the kernel rbtree code	2024-05-08 08:41:27 -07:00
slab.c
str_error_r.c
string.c
vsprintf.c
zalloc.c