From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Kuniyuki Iwashima <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Mahesh Bandewar <maheshb@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v1 net-next] selftest: net: Use port outside of the default ip_local_ports in csum.c.
Date: Sat, 11 Apr 2026 15:18:56 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.15ccd7e646278@gmail.com> (raw)
In-Reply-To: <20260410215420.1698033-1-kuniyu@google.com>
Kuniyuki Iwashima wrote:
> csum.c binds a socket on a fixed port in init_net to test
> the csum offload feature between two machines.
>
> In our testbed, the test sometimes fails with -EADDRINUSE.
>
> bind r: Address already in use
> bind dgram 6: Address already in use
>
> The fixed ports (33000, 33001, 34000) are all within the default
> ip_local_ports range (32768 ~ 60999), and other processes may
> happen to be using them.
>
> Let's use ports outside of the default ip_local_ports range to
> deflake the test.
>
> # cat /etc/services | grep -E "(13000|13001|13002)" | echo no service
> no service
> # rpm -qf /etc/services
> setup-2.15.0-28.fc44.noarch
>
> We could add an option to specify ports if needed.
>
> Suggested-by: Mahesh Bandewar <maheshb@google.com>
> Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com>
> ---
> tools/testing/selftests/net/lib/csum.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/net/lib/csum.c b/tools/testing/selftests/net/lib/csum.c
> index e28884ce3ab3..4e044689bc37 100644
> --- a/tools/testing/selftests/net/lib/csum.c
> +++ b/tools/testing/selftests/net/lib/csum.c
> @@ -105,9 +105,9 @@ static char *cfg_mac_src;
> static int cfg_proto = IPPROTO_UDP;
> static int cfg_payload_char = 'a';
> static int cfg_payload_len = 100;
> -static uint16_t cfg_port_dst = 34000;
This is paired with wait_port_listen(3400, .. in
tools/testing/selftests/drivers/net/hw/csum.py
It is also used in tools/testing/selftests/drivers/net/hw/tso.py,
which uses rand_port to select a port.
Probably more robust to indeed add an option to specify a port, and
in all callers use rand_port(s).
> -static uint16_t cfg_port_src = 33000;
> -static uint16_t cfg_port_src_encap = 33001;
> +static uint16_t cfg_port_dst = 13000;
> +static uint16_t cfg_port_src = 13001;
> +static uint16_t cfg_port_src_encap = 13002;
> static unsigned int cfg_random_seed;
> static int cfg_rcvbuf = 1 << 22; /* be able to queue large cfg_num_pkt */
> static bool cfg_send_pfpacket;
> --
> 2.53.0.1213.gd9a14994de-goog
>
next prev parent reply other threads:[~2026-04-11 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 21:54 [PATCH v1 net-next] selftest: net: Use port outside of the default ip_local_ports in csum.c Kuniyuki Iwashima
2026-04-11 19:18 ` Willem de Bruijn [this message]
2026-04-12 16:47 ` Jakub Kicinski
2026-04-12 20:56 ` Kuniyuki Iwashima
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=willemdebruijn.kernel.15ccd7e646278@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.