From: Boris Sukholitko <boris.sukholitko@broadcom.com>
To: netfilter-devel@vger.kernel.org
Cc: Ilya Lifshits <ilya.lifshits@broadcom.com>,
Boris Sukholitko <boris.sukholitko@broadcom.com>
Subject: [PATCH nf-next v2 0/4] selftest: netfilter: small test tweaks
Date: Thu, 4 May 2023 11:48:10 +0300 [thread overview]
Message-ID: <20230504084814.41487-1-boris.sukholitko@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Hi,
These patches allow nft_flowtable.sh test script to work in busybox environment
(patches 1-2).
More exact wait for netcat running in the background is in patch 3.
Small adaptive sleep optimization (patch 4) helps with running on busy servers
and cuts default sleep time a bit.
Thanks,
Boris.
- v2:
- extracted from controversial dscp offload series
- added Acked-by: Florian Westphal <fw.de> on patch 4
Boris Sukholitko (4):
selftest: netfilter: use /proc for pid checking
selftest: netfilter: no need for ps -x option
selftest: netfilter: wait for specific nc pids
selftest: netfilter: monitor result file sizes
.../selftests/netfilter/nft_flowtable.sh | 21 +++++++++++++------
1 file changed, 15 insertions(+), 6 deletions(-)
base-commit: 19c60fdee5db881a99a9c39fb31942a530d20c63
--
2.32.0
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next reply other threads:[~2023-05-04 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 8:48 Boris Sukholitko [this message]
2023-05-04 8:48 ` [PATCH nf-next v2 1/4] selftest: netfilter: use /proc for pid checking Boris Sukholitko
2023-05-04 8:48 ` [PATCH nf-next v2 2/4] selftest: netfilter: no need for ps -x option Boris Sukholitko
2023-05-04 8:48 ` [PATCH nf-next v2 3/4] selftest: netfilter: wait for specific nc pids Boris Sukholitko
2023-05-04 8:48 ` [PATCH nf-next v2 4/4] selftest: netfilter: monitor result file sizes Boris Sukholitko
2023-05-10 7:09 ` [PATCH nf-next v2 0/4] selftest: netfilter: small test tweaks Pablo Neira Ayuso
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=20230504084814.41487-1-boris.sukholitko@broadcom.com \
--to=boris.sukholitko@broadcom.com \
--cc=ilya.lifshits@broadcom.com \
--cc=netfilter-devel@vger.kernel.org \
/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