From: Florian Westphal <fw@strlen.de>
To: Yi Chen <yiche@redhat.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2] tests: shell: Verify limit statement with new test case.
Date: Sat, 21 Jun 2025 13:37:29 +0200 [thread overview]
Message-ID: <aFaZeVki08veClUU@strlen.de> (raw)
In-Reply-To: <20250620164730.50041-1-yiche@redhat.com>
Yi Chen <yiche@redhat.com> wrote:
> 1. Add rate_limit test case.
> 2. Consolidate frequently used functions in helper/lib.sh
> 3. Introduce NFT_TEST_LIBRARY_FILE variable to source helper/lib.sh in
> tests.
> 4. Replace sleep with wait_local_port_listen().
> 5. Other fixes: nft->$NFT; add dumps/*.nodump files
This is hard to review, can you split this in multiple patches
to make it easier? We prefer to have one logical patch per change.
For example:
Patch1: don't use system nft binary
You can also add the .nodump file in this patch.
Patch 2:
Consolidate frequently used functions in helper/lib.sh
This also adds the NFT_TEST_LIBRARY_FILE environment variable
and would switch nat_ftp and flowtables to use it.
Patch 3: add and use wait_local_port_listen
This would add the helper and convert sleeps after listener to use
the new helper.
Patch 4:
Adds the new rate_limit test case and a nodump file.
I mean, the changes look good to me but I think its too big
for one single change.
prev parent reply other threads:[~2025-06-21 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 10:41 [PATCH] tests: shell: Add a test case to verify the limit statement Yi Chen
2025-06-18 22:46 ` Florian Westphal
[not found] ` <CAJsUoE0etJbdwHsHFHDnY1CkdmAXLJy7PunwQg9Me4n-AMPWmQ@mail.gmail.com>
2025-06-20 9:31 ` Florian Westphal
[not found] ` <CAJsUoE1ZChx7VcbZLnBpwbbkhGmfVVzomHUu7GP8xQCs00gZrw@mail.gmail.com>
2025-06-20 12:30 ` Yi Chen
2025-06-20 16:40 ` [PATCH] tests: shell: Verify limit statement with new test case Yi Chen
2025-06-20 16:47 ` [PATCH v2] " Yi Chen
2025-06-21 11:37 ` Florian Westphal [this message]
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=aFaZeVki08veClUU@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=yiche@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 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.