Hide Forgot
Description of problem: When use the test programs under ksamples/bpf, there's a warning, but seems no impact to the function. libbpf: elf: skipping unrecognized data section(16) .eh_frame libbpf: elf: skipping relo section(17) .rel.eh_frame for section(16) .eh_frame Version-Release number of selected component (if applicable): [root@netqe2 bpf]# uname -r 4.18.0-315.el8.x86_64 How reproducible: 100% Steps to Reproduce: 1. try any of the test xdp program like "./xdp_rxq_info --dev ens5f0 --action XDP_DROP" Actual results: a warning poped up Expected results: no warning Additional info:
This is a known issue upstream because of the way the samples are compiled. The error itself is completely harmless, but I agree it's confusing. To fix this, either the samples Makefile needs to be changed, or libbpf needs to be taught to ignore those sections. I sent a patch with the latter change, lets see what upstream thinks: https://lore.kernel.org/bpf/20210629110923.580029-1-toke@redhat.com/T/
(In reply to Toke Høiland-Jørgensen from comment #1) > This is a known issue upstream because of the way the samples are compiled. > The error itself is completely harmless, but I agree it's confusing. To fix > this, either the samples Makefile needs to be changed, or libbpf needs to be > taught to ignore those sections. > > I sent a patch with the latter change, lets see what upstream thinks: > https://lore.kernel.org/bpf/20210629110923.580029-1-toke@redhat.com/T/ Thanks, Toke! Glad to know we've already have a patch for this:)
Samples are now fixed upstream by this commit: https://git.kernel.org/bpf/bpf/c/5a0ae9872d5c Jiri, do you think you could pull this out-of-order into one of the BPF backports? It's a pretty trivial fix, so would be good to not have to wait for the 5.14 backports to get it fixed up in RHEL...
as discussed on the mtg, let's ask jbenc in MR
Please include it as a separate fix. We can use this bz to submit it against.
Submitting as MR https://gitlab.com/redhat/rhel/src/kernel/rhel-8/-/merge_requests/108 Zhiqian, can it have qa_ack?
(In reply to Yauheni Kaliuta from comment #6) > Submitting as MR > https://gitlab.com/redhat/rhel/src/kernel/rhel-8/-/merge_requests/108 > Zhiqian, can it have qa_ack? Sure, set qa_ack
https://beaker.engineering.redhat.com/jobs/5694267 :: [ 07:22:29 ] :: [ BEGIN ] :: Running 'ebpf_xdp_test_XDP_DROP' ebpf_xdp_test_XDP_DROP()... /usr/libexec/ksamples/bpf /mnt/tests/kernel/networking/ebpf_xdp/sanity ./xdp_rxq_info --dev ens1f0 --action XDP_DROP root 40603 14847 0 07:22 ? 00:00:00 ./xdp_rxq_info --dev ens1f0 --action XDP_DROP root 40605 14847 0 07:22 ? 00:00:00 grep xdp_rxq_info /mnt/tests/kernel/networking/ebpf_xdp/sanity 3: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 xdp qdisc mq state UP mode DEFAULT group default qlen 1000 3: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 xdp qdisc mq state UP mode DEFAULT group default qlen 1000 wait for ens1f0 sec 0 3: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 xdp qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 00:de:ad:de:ad:01 brd ff:ff:ff:ff:ff:ff permaddr 40:a6:b7:2f:b9:20 prog/xdp id 105 tag 943df0a1ce7ea5c2 jited Wait 0 secs until port becomes UP 3: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 xdp qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 00:de:ad:de:ad:01 brd ff:ff:ff:ff:ff:ff permaddr 40:a6:b7:2f:b9:20 prog/xdp id 105 tag 943df0a1ce7ea5c2 jited SYNC_NC: sync_set client test_XDP_DROP SYNC_NC: sent "test_XDP_DROP" to netqe2.knqe.lab.eng.bos.redhat.com SYNC_NC: sync_wait client test_XDP_DROP SYNC_NC: waiting "netqe2.knqe.lab.eng.bos.redhat.com" SYNC_NC: got "test_XDP_DROP" from netqe2.knqe.lab.eng.bos.redhat.com No libbpf: elf: skipping unrecognized data section(16) .eh_frame anymore, set this to verified:tested
https://beaker.engineering.redhat.com/jobs/5729147 no more warnings, set 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 (Moderate: kernel security, 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/RHSA-2021:4356