On Sat, Nov 8, 2025 at 10:49 PM Salvatore Bonaccorso <[email protected]> wrote: > > Hi, > > On Tue, Oct 21, 2025 at 12:51:32PM +0200, Fernando Fernandez Mancera wrote: > > > > > > On 10/20/25 11:31 PM, mc36 wrote: > > > hi, > > > > > > On 10/20/25 11:04, Jason Xing wrote: > > > > > > > > I followed your steps you attached in your code: > > > > ////// gcc xskInt.c -lxdp > > > > ////// sudo ip link add veth1 type veth > > > > ////// sudo ip link set veth0 up > > > > ////// sudo ip link set veth1 up > > > > > > ip link set dev veth1 address 3a:10:5c:53:b3:5c > > > > > > > ////// sudo ./a.out > > > > > > > that will do the trick on a recent kerlek.... > > > > > > its the destination mac in the c code.... > > > > > > ps: chaining in the original reporter from the fedora land..... > > > > > > > > > have a nice day, > > > > > > cs > > > > > > > > > > hi, FWIW I have reproduced this and I bisected it, issue was introduced at > > 30f241fcf52aaaef7ac16e66530faa11be78a865 - working on a patch. > > Just a qustion in particular for the stable series shipping the commit > (now only 6.17.y relevant at this point since 6.16.y is EOL): Give the > proper fix will take a bit more time to develop, would it make sense > to at least revert the offending commit in the stable series as the > issue is, unless I missunderstood the report, remotely(?) triggerable > denial of service? > > Or do I miss something here?
We've been working on this already. Please find the patches at https://lore.kernel.org/all/[email protected]/ Yes, my solution is to revert first and apply a pre-allocate array to temporarily store the descriptors that will be published at the tx completion phase. If you also care about this, please feel free to review the whole idea. As long as everyone is on board, I will send an official version with more detailed updates. I'm still waiting for more suggestions :) Thanks, Jason
