On Thu, Oct 08, 2026 at 09:04:42AM +0200, Eelco Chaudron wrote: > > > On 7 Oct 2026, at 15:43, Simon Horman via dev wrote: > > > It appears that there is may be some delay in cleanup can results in > > this test failing because the port cannot be recreated. > > > > # make check-afxdp TESTSUITEFLAGS="2 -v" > > ... > > 2. system-afxdp.at:27: testing AF_XDP - ping between pmd and non-pmd ports > > ... > > 2026-10-07T10:38:10.997Z|00099|netdev_afxdp|ERR|xsk_socket__create failed > > (Device or resource busy) mode: generic, qid: 0 > > > > My LLM tells me this is an issue with older kernels delaying cleanup. > > But it also calaimed this is addressed in the v5.15 kernel, while > > my kernel is much newer than that. So who knows. > > > > In any case I did I did not investigate beyond verifying that this patch > > addresses the failure I was seeing. > > > > Observed on RHEL 10.2 on aarch64. > > RHEL 10.2 ships with a heavily patched 6.12.0 kernel. > > > > Assisted-by: LLM > > Signed-off-by: Simon Horman <[email protected]> > > Hi Simon, > > Thanks for the patch and for looking into this. However, we are trying to > get rid of all the sleeps in the unit tests. Would it be possible to wait for > the device to be removed? Maybe something like; > > OVS_WAIT_WHILE([ip link show ovs-p0]).
Perhaps strangely it seems that condition is not met. This one is: OVS_WAIT_WHILE([ovs-vsctl list-ports br0 | grep -q ovs-p0]) Curiously, straight away. But without that line the test fails in my environment. > > Also, for OVS, the Assisted-by tag should have the following format: > > Assisted-by: Name of model, and/or AI Code Assistant Ack, got it. ... _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
