netdev - ixgbe driver stops sending normal data when using xsk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL+tcoCTHTptwmok9vhp7GEwQgMhNsBJxT3PStJDeVOLR_-Q3g@mail.gmail.com>
Date: Wed, 16 Jul 2025 11:41:42 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: Jakub Kicinski <kuba@...nel.org>, Stanislav Fomichev <sdf@...ichev.me>, 
	"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>, przemyslaw.kitszel@...el.com, 
	Maciej Fijalkowski <maciej.fijalkowski@...el.com>
Cc: intel-wired-lan@...ts.osuosl.org, netdev <netdev@...r.kernel.org>
Subject: ixgbe driver stops sending normal data when using xsk

Hi all,

I'm currently faced with one tough issue caused by zero copy mode in
xsk with ixgbe driver loaded. The case is that if we use xdpsock to
send descs, nearly at the same time normal packets from other tx
queues cannot be transmitted/completed at all.

Here is how I try:
1. run iperf or ping to see if the transmission is successful.
2. then run "timeout 5 ./xdpsock -i enp2s0f0 -t  -z -s 64"

You will obviously find the whole machine loses connection. It can
only recover as soon as the xdpsock is stopped due to timeout.

I tried a lot and then traced down to this line in ixgbe driver:
ixgbe_clean_tx_irq()
    -> if (!(eop_desc->wb.status & cpu_to_le32(IXGBE_TXD_STAT_DD)))
            break;
The above line always 'breaks' the sending process.

I also managed to make the external ixgbe 6.15 work and it turned out
to be the same issue as before.

I have no idea on how to analyze further in this driver. Could someone
point out a direction that I can take? Is it a known issue?

Thanks,
Jason