Hide Forgot
Description of problem: Like before we anticipate shipping an updated version of xdp-tools for RHEL 8.5 - this tracks that packaging effort...
Set DTM fairly close to beta as the idea is to collect everything that's happened in the upstream repo until that date. Zhiqian, let me know if it's too close to beta, I don't mind moving it a week or two...
(In reply to Toke Høiland-Jørgensen from comment #1) > Set DTM fairly close to beta as the idea is to collect everything that's > happened in the upstream repo until that date. Zhiqian, let me know if it's > too close to beta, I don't mind moving it a week or two... I suggest set DTM to 21 or 22, gives me one or two weeks to test it:) I'll set the ITM to 24
OK, updating... :)
xdp-tools-1.2.0-1.el8 is now in rhel-8.5.0-candidate
Ah, oops, totally forgot to create the errata, sorry about that! Did so now, and assigned it to you; that should also include the link to the brew build :)
(In reply to Toke Høiland-Jørgensen from comment #8) > Ah, oops, totally forgot to create the errata, sorry about that! Did so now, > and assigned it to you; that should also include the link to the brew build > :) Great, thanks Toke! I ran the test for this build. And it seems in xdpdump, I cannot listen to the program "xdp_dispatcher" anymore, I can listen to the dispatcher program before, is that expected? [root@netqe3 ~]# uname -r 4.18.0-321.el8.x86_64 [root@netqe3 ~]# rpm -q xdp-tools xdp-tools-1.2.0-1.el8.x86_64 [root@netqe3 ~]# [root@netqe3 ~]# xdpdump -i ens1f0 -p "xdp_dispatcher" ERROR: Can't attach XDP trace fentry function: Device or resource busy [root@netqe3 ~]# xdp-loader status CURRENT XDP PROGRAM STATUS: Interface Prio Program name Mode ID Tag Chain actions -------------------------------------------------------------------------------------- lo <No XDP program loaded!> eno1 <No XDP program loaded!> eno2 <No XDP program loaded!> ens1f0 xdp_dispatcher skb 1411 94d5f00c20184d17 => 10 xdpfilt_alw_all 1423 0b394f43ab24501c XDP_PASS eno3 <No XDP program loaded!> ens1f1 <No XDP program loaded!> ens5f0 <No XDP program loaded!> eno4 <No XDP program loaded!> ens5f1 <No XDP program loaded!> ens4f0 <No XDP program loaded!> ens4f1 <No XDP program loaded!> ens3np0 <No XDP program loaded!> ens3np1 <No XDP program loaded!> [root@netqe3 ~]# xdpdump -i ens1f0 -p "xdpfilt_alw_all" listening on ens1f0, ingress XDP program ID 1423 func xdpfilt_alw_all, capture mode entry, capture size 262144 bytes ^C 0 packets captured 0 packets dropped by perf ring
Hmm, not sure if that's expected for xdpdump. Eelco should know...
(In reply to Toke Høiland-Jørgensen from comment #11) > Hmm, not sure if that's expected for xdpdump. Eelco should know... This was related to a change you made Toke ;) If there is only one program loaded, the xdp_dispatcher program is not executed/used, hence you can not attach to it. If you would load another program, so you would have two programs on the same interface, you should be able to attach to the dispatcher again.
Ahh, right, of course; my bad! Right, so this is expected, Zhiqian :)
Got it! Thanks, Toke&Eelco!
nfp: https://beaker.engineering.redhat.com/jobs/5630773 sfc: https://beaker.engineering.redhat.com/jobs/5630772 cx6: https://beaker.engineering.redhat.com/jobs/5630769 cx5: https://beaker.engineering.redhat.com/jobs/5630768 ice: https://beaker.engineering.redhat.com/jobs/5630766 qede: https://beaker.engineering.redhat.com/jobs/5641261 bnxt: https://beaker.engineering.redhat.com/jobs/5640472 i40e: https://beaker.engineering.redhat.com/jobs/5630759 ixgbe: https://beaker.engineering.redhat.com/jobs/5630756 Test pass, the failed cases are automation issues, I'm fixing it. 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 (xdp-tools 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/RHEA-2021:4303