Bug 2065638
Summary: | libbpf SEGFAULT with fully stripped BPF object | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Felix Maurer <fmaurer> |
Component: | libbpf | Assignee: | Viktor Malik <vmalik> |
Status: | CLOSED ERRATA | QA Contact: | Zhiqian Guan <zhguan> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.0 | CC: | vmalik, zhguan |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libbpf-0.6.0-1.el9 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-15 11:21:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2069045 | ||
Bug Blocks: |
Description
Felix Maurer
2022-03-18 11:43:07 UTC
Requires upstream commit: 03e601f48b2 libbpf: Don't crash on object files with no symbol tables which should be pulled in as a part of BPF 5.16 rebase. libbpf 0.6.0 should contain the commit mentioned above Tested on kernel 5.14.0-130.el9.x86_64 [root@netqe12 ~]# cd /usr/libexec/kselftests/bpf [root@netqe12 bpf]# ip link add dev veth0 type veth peer name veth1 [root@netqe12 bpf]# strip sample_map_ret0.o [root@netqe12 bpf]# ip link set dev veth0 xdp obj sample_map_ret0.o sec .text verbose libbpf: loading sample_map_ret0.o libbpf: elf: couldn't find symbol table in sample_map_ret0.o, stripped object file? ERROR: opening BPF object file failed The error msg looks more friendly. Since the patch has already been merged by bpf update, so mark this as testOnly. Based on comment3, move this to VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (libbpf bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8364 |