Subject: Re: [PATCH net-next] selftests: hw-net: rss-input-xfrm: try to enable the xfrm at the start

From: Jakub Kicinski <[email-masked]>
Date: Mon, 5 Jan 2026 17:09:58 -0800

On Sun,  4 Jan 2026 10:46:00 -0800 Jakub Kicinski wrote:
> The test currently SKIPs if the symmetric RSS xfrm is not enabled
> by default. This leads to spurious SKIPs in the Intel CI reporting
> results to NIPA.
> 
> Testing on CX7:
> 
>  # ./drivers/net/hw/rss_input_xfrm.py
>   TAP version 13
>   1..2
>   ok 1 rss_input_xfrm.test_rss_input_xfrm_ipv4 # SKIP Test requires IPv4 connectivity
>   # Sym input xfrm already enabled: {'sym-or-xor'}
>   ok 2 rss_input_xfrm.test_rss_input_xfrm_ipv6
>   # Totals: pass:1 fail:0 xfail:0 xpass:0 skip:1 error:0
> 
>  # ethtool -X eth0 xfrm none
> 
>  # ./drivers/net/hw/rss_input_xfrm.py
>   TAP version 13
>   1..2
>   ok 1 rss_input_xfrm.test_rss_input_xfrm_ipv4 # SKIP Test requires IPv4 connectivity
>   # Sym input xfrm configured: {'sym-or-xor'}
>   ok 2 rss_input_xfrm.test_rss_input_xfrm_ipv6
>   # Totals: pass:1 fail:0 xfail:0 xpass:0 skip:1 error:0

Weird, looking at Intel's results for net-next-hw-2026-01-06--00-00
it's still skipping. What's going on Intel folks? This test seems to
skip / pass on your setup rather randomly:
https://netdev.bots.linux.dev/contest.html?test=rss-input-xfrm-py

While I have you - could you configure your HTTP server to serve the
logs as plain text? FWIW for nginx in NIPA we use:

location /logs {
    default_type        text/plain;
    charset utf-8;

    location ~ (stderr|stdout|retcode|summary) {
        gzip on;
        gzip_min_length 16000;
        gzip_types text/plain;
	charset utf-8;
    }
}

Otherwise every time we click on the link to your logs in NIPA 
the browser downloads the logs instead of displaying them.