public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [RFC PATCH 0/1] IDPF + SWIOTLB Bug
@ 2026-02-27  2:59 Steve Rutherford
  2026-02-27  2:59 ` [RFC PATCH 1/1] Fix header clobber in IDPF with SWIOTLB enabled Steve Rutherford
  0 siblings, 1 reply; 3+ messages in thread
From: Steve Rutherford @ 2026-02-27  2:59 UTC (permalink / raw)
  To: anthony.l.nguyen, przemyslaw.kitszel, aleksander.lobakin
  Cc: andrew+netdev, davem, edumazet, kuba, pabeni, intel-wired-lan,
	netdev, linux-kernel, Steve Rutherford

Found an issue with the IDPF driver when SWIOTLB is enabled. The issue
results in empty headers for packets that hit the split queue workaround
path. It's caused by a spurious sync in that path. The header is synced
from the SWIOTLB even when the header was shoved into the payload.

I cooked up a sample patch, but I'm not an expert in this driver, so I have
no idea if it's the right solution. It did allow my QEMU VM to boot with a
superficially functional passed-through IDPF NIC and SWIOTLB=force.

The patch was written against COS's 6.12, so I assume that it will not
apply cleanly elsewhere, but I figured a wrong sample patch was better than
a long paragraph describing the same thing. My read of more recent kernels
is that this problem is still present, but could be mistaken.

Steve Rutherford (1):
  Fix header clobber in IDPF with SWIOTLB enabled

 drivers/net/ethernet/intel/idpf/idpf_txrx.c | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

-- 
2.53.0.473.g4a7958ca14-goog


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-02-27 17:07 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-27  2:59 [RFC PATCH 0/1] IDPF + SWIOTLB Bug Steve Rutherford
2026-02-27  2:59 ` [RFC PATCH 1/1] Fix header clobber in IDPF with SWIOTLB enabled Steve Rutherford
2026-02-27 17:07   ` [Intel-wired-lan] " Loktionov, Aleksandr

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox