From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
willemdebruijn.kernel@gmail.com, ecree.xilinx@gmail.com,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next 1/4] selftests: drv-net: try to check if port is in use
Date: Sun, 23 Jun 2024 03:34:23 -0400 [thread overview]
Message-ID: <6677cfffbc25a_33363c294d@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20240620232902.1343834-2-kuba@kernel.org>
Jakub Kicinski wrote:
> We use random ports for communication. As Willem predicted
> this leads to occasional failures. Try to check if port is
> already in use by opening a socket and binding to that port.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> tools/testing/selftests/net/lib/py/utils.py | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/lib/py/utils.py b/tools/testing/selftests/net/lib/py/utils.py
> index 0540ea24921d..9fa9ec720c89 100644
> --- a/tools/testing/selftests/net/lib/py/utils.py
> +++ b/tools/testing/selftests/net/lib/py/utils.py
> @@ -3,6 +3,7 @@
> import json as _json
> import random
> import re
> +import socket
> import subprocess
> import time
>
> @@ -81,7 +82,17 @@ import time
> """
> Get unprivileged port, for now just random, one day we may decide to check if used.
> """
> - return random.randint(10000, 65535)
> + while True:
> + port = random.randint(10000, 65535)
> + try:
> + with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:
> + s.bind(("", port))
> + with socket.socket(socket.AF_INET6, socket.SOCK_STREAM) as s:
> + s.bind(("", port))
Is the separate AF_INET needed? As AF_INET6 is not IPV6_V6ONLY.
The following correctly fails in the second bind
with socket.socket(socket.AF_INET6, socket.SOCK_STREAM) as s6:
s6.bind(("", 8000))
with socket.socket(socket.AF_INET6, socket.SOCK_STREAM) as s4:
s4.bind(("", 8000))
> + return port
> + except OSError as e:
> + if e.errno != 98: # already in use
> + raise
>
>
> def wait_port_listen(port, proto="tcp", ns=None, host=None, sleep=0.005, deadline=5):
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-06-23 7:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 23:28 [PATCH net-next 0/4] selftests: drv-net: rss_ctx: add tests for RSS contexts Jakub Kicinski
2024-06-20 23:28 ` [PATCH net-next 1/4] selftests: drv-net: try to check if port is in use Jakub Kicinski
2024-06-21 1:52 ` David Wei
2024-06-23 7:34 ` Willem de Bruijn [this message]
2024-06-24 13:59 ` Przemek Kitszel
2024-06-20 23:28 ` [PATCH net-next 2/4] selftests: drv-net: add helper to wait for HW stats to sync Jakub Kicinski
2024-06-23 7:37 ` Willem de Bruijn
2024-06-24 14:43 ` Jakub Kicinski
2024-06-20 23:29 ` [PATCH net-next 3/4] selftests: drv-net: add ability to wait for at least N packets to load gen Jakub Kicinski
2024-06-21 1:14 ` David Wei
2024-06-20 23:29 ` [PATCH net-next 4/4] selftests: drv-net: rss_ctx: add tests for RSS configuration and contexts Jakub Kicinski
2024-06-21 1:52 ` David Wei
2024-06-21 2:26 ` Jakub Kicinski
2024-06-23 8:03 ` Willem de Bruijn
2024-06-24 14:50 ` Jakub Kicinski
2024-06-24 16:02 ` Jakub Kicinski
2024-06-24 12:55 ` Edward Cree
2024-06-24 14:54 ` Jakub Kicinski
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=6677cfffbc25a_33363c294d@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).