On 5/22/25 3:53 PM, Jakub Kicinski wrote: > On Thu, 22 May 2025 12:09:01 +0200 Paolo Abeni wrote: >> Recently the nipa CI infra went through some tuning, and the mentioned >> self-test now often fails. >> >> As I could not find any applied or pending relevant change, I have a >> vague suspect that the timeout applied to the server command now >> triggers due to different timing. Could you please have a look? > > Oh, I was just staring at: > https://lore.kernel.org/all/20250522031835.4395-1-shiming.cheng@xxxxxxxxxxxx/ > do you think it's not that? It's not obvious to me. The failing test case is: tcp via loopback and re-queueing There should be no S/W segmentation there, as the loopback interface exposes TSO. @Florian, I'm sorry I should have mentioned explicitly the failing test before. Sample failures: https://netdev-3.bots.linux.dev/vmksft-nf/results/131921/2-nft-queue-sh/stdout https://netdev-3.bots.linux.dev/vmksft-nf/results/131741/2-nft-queue-sh/stdout I was wondering about this timeout specifically: https://elixir.bootlin.com/linux/v6.15-rc7/source/tools/testing/selftests/net/netfilter/nft_queue.sh#L329 > I'll hide both that patch and Florian's fix from the queue for now, > for a test. Fine by me. Thanks, Paolo
