All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Nikolaos Gkarlis <nickgarlis@gmail.com>
Cc: netfilter-devel@vger.kernel.org, pablo@netfilter.org, fmancera@suse.de
Subject: Re: [PATCH v2 2/2] selftests: netfilter: add nfnetlink ACK handling tests
Date: Sun, 5 Oct 2025 13:42:38 +0200	[thread overview]
Message-ID: <aOJZn0TLARyv5Ocj@strlen.de> (raw)
In-Reply-To: <CA+jwDR=ryt_yTj7Y7B9ZdbKVeb7XsN40zASO1MXC75suYaceXA@mail.gmail.com>

Nikolaos Gkarlis <nickgarlis@gmail.com> wrote:
> Florian Westphal <fw@strlen.de> wrote:
> > Is this to exercise replay path?
> > Perhaps add a comment to the subtest that depends on this.
> 
> Yes, that is the goal. I can add a comment to the test explaining that.

Thanks!

> verifies the number of ACKs returned and their order, which is what
> bf2ac490d28c broke. I have tested both builtin and non-existent cases.

Great.

> What do you think about something like this?
> 
> +++ b/tools/testing/selftests/net/netfilter/nfnetlink.sh
> @@ -0,0 +1,5 @@
> +#!/bin/bash
> +
> +# If nft_ct is a module and is loaded, remove it to test module auto-loading

Looks good, can you also mention that if removal doesn't work this is
ok?

> +lsmod | grep -q "^nft_ct\b" && rmmod nft_ct

You could just "rmmod nft_ct 2>/dev/null" with
above comment in place.

> +./nfnetlink

Since you need the shell wraper for the rmmod you could
also make this

unshare -n ./nfnetlink and not do it in the .c setup
function.  Your call.

> I can send a v3 if that looks okay to you.

Yes please.  You can just send a v3 of the test case,
no need to resend the fix.

  reply	other threads:[~2025-10-05 11:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01 21:15 [PATCH] netfilter: nfnetlink: always ACK batch end if requested Nikolaos Gkarlis
2025-10-02  9:48 ` Fernando Fernandez Mancera
2025-10-02 10:41   ` Nikolaos Gkarlis
2025-10-02 11:03     ` Fernando Fernandez Mancera
2025-10-04  9:26       ` [PATCH v2 0/2] " Nikolaos Gkarlis
2025-10-04  9:26         ` [PATCH v2 1/2] netfilter: nfnetlink: " Nikolaos Gkarlis
2025-10-04  9:26         ` [PATCH v2 2/2] selftests: netfilter: add nfnetlink ACK handling tests Nikolaos Gkarlis
2025-10-04 10:46           ` Florian Westphal
2025-10-04 11:08             ` Nikolaos Gkarlis
2025-10-04 12:26               ` Florian Westphal
2025-10-05 10:43                 ` Nikolaos Gkarlis
2025-10-05 11:42                   ` Florian Westphal [this message]
2025-10-05 12:54                     ` [PATCH v3] " Nikolaos Gkarlis
2025-10-08 10:26                       ` Florian Westphal
2025-10-08 10:37                         ` Nikolaos Gkarlis
2025-10-08 10:39                           ` Florian Westphal
2026-02-04 16:33                       ` Florian Westphal
2025-10-04  9:38       ` [PATCH v2 0/2] always ACK batch end if requested Nikolaos Gkarlis
2025-10-02 10:10 ` [PATCH] netfilter: nfnetlink: " Florian Westphal
2025-10-02 10:46   ` Nikolaos Gkarlis
2025-10-07 20:33 ` Pablo Neira Ayuso
2025-10-08  7:28   ` Florian Westphal
2025-10-08 11:33     ` Pablo Neira Ayuso
2025-10-08 13:35       ` Donald Hunter
2025-10-08 14:50         ` Florian Westphal
2025-10-08  8:41   ` Nikolaos Gkarlis
2025-10-08 11:09     ` Pablo Neira Ayuso
2025-10-08 14:50       ` Nikolaos Gkarlis

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=aOJZn0TLARyv5Ocj@strlen.de \
    --to=fw@strlen.de \
    --cc=fmancera@suse.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=nickgarlis@gmail.com \
    --cc=pablo@netfilter.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 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.