[PATCH bpf-next 0/4] selftests/bpf: Fix compilation with RELEASE=1

[Viktor Malik <vmalik@redhat.com>]

When compiling BPF selftests with RELEASE=1 (which most notably adds
-O2), GCC reports several warnings. These are by default treated as
errors and abort the compilation.

This series fixes all of the issues such that selftests can be compiled
with RELEASE=1.

Viktor Malik (4):
  selftests/bpf: Check malloc result with ASSERT_NEQ in test_loader
  selftests/bpf: Check malloc result with ASSERT_NEQ in test_sha256
  selftests/bpf: Silence array bounds warning in global_map_resize
  selftests/bpf: Silence maybe-uninitialized compiler warning in
    libarena

 .../selftests/bpf/libarena/include/libarena/userspace.h   | 2 +-
 .../testing/selftests/bpf/prog_tests/global_map_resize.c  | 8 ++++++--
 tools/testing/selftests/bpf/prog_tests/sha256.c           | 4 ++--
 tools/testing/selftests/bpf/test_loader.c                 | 2 +-
 4 files changed, 10 insertions(+), 6 deletions(-)

-- 
2.54.0