From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
willemdebruijn.kernel@gmail.com, ecree.xilinx@gmail.com,
dw@davidwei.uk, przemyslaw.kitszel@intel.com,
michael.chan@broadcom.com, andrew.gospodarek@broadcom.com,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v2 1/4] selftests: drv-net: try to check if port is in use
Date: Mon, 24 Jun 2024 18:02:07 -0700 [thread overview]
Message-ID: <20240625010210.2002310-2-kuba@kernel.org> (raw)
In-Reply-To: <20240625010210.2002310-1-kuba@kernel.org>
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>
---
v2:
- remove v4 check (Willem)
- update comment (David, Przemek)
- cap the iterations (Przemek)
---
tools/testing/selftests/net/lib/py/utils.py | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/net/lib/py/utils.py b/tools/testing/selftests/net/lib/py/utils.py
index 0540ea24921d..16907b51e034 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
@@ -79,9 +80,18 @@ import time
def rand_port():
"""
- Get unprivileged port, for now just random, one day we may decide to check if used.
+ Get a random unprivileged port, try to make sure it's not already used.
"""
- return random.randint(10000, 65535)
+ for _ in range(1000):
+ port = random.randint(10000, 65535)
+ try:
+ with socket.socket(socket.AF_INET6, socket.SOCK_STREAM) as s:
+ s.bind(("", port))
+ return port
+ except OSError as e:
+ if e.errno != 98: # already in use
+ raise
+ raise Exception("Can't find any free unprivileged port")
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-25 1:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 1:02 [PATCH net-next v2 0/4] selftests: drv-net: rss_ctx: add tests for RSS contexts Jakub Kicinski
2024-06-25 1:02 ` Jakub Kicinski [this message]
2024-06-25 6:57 ` [PATCH net-next v2 1/4] selftests: drv-net: try to check if port is in use Przemek Kitszel
2024-06-25 8:02 ` Breno Leitao
2024-06-25 1:02 ` [PATCH net-next v2 2/4] selftests: drv-net: add helper to wait for HW stats to sync Jakub Kicinski
2024-06-25 10:04 ` Petr Machata
2024-06-25 1:02 ` [PATCH net-next v2 3/4] selftests: drv-net: add ability to wait for at least N packets to load gen Jakub Kicinski
2024-06-25 8:05 ` Breno Leitao
2024-06-25 8:53 ` Willem de Bruijn
2024-06-25 1:02 ` [PATCH net-next v2 4/4] selftests: drv-net: rss_ctx: add tests for RSS configuration and contexts Jakub Kicinski
2024-06-25 10:42 ` Petr Machata
2024-06-25 13:50 ` Jakub Kicinski
2024-06-25 14:43 ` Petr Machata
2024-06-25 17:06 ` Jakub Kicinski
2024-06-25 17:41 ` Jakub Kicinski
2024-06-26 8:42 ` Petr Machata
2024-06-25 1:40 ` [PATCH net-next v2 0/4] selftests: drv-net: rss_ctx: add tests for RSS contexts Jakub Kicinski
2024-06-25 3:42 ` Michael Chan
2024-06-25 8:52 ` Willem de Bruijn
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=20240625010210.2002310-2-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=willemdebruijn.kernel@gmail.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.