public inbox for netfilter-devel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [nf-next PATCH] netfilter: nfnetlink_hook: Dump nat type chains
Date: Fri, 20 Mar 2026 12:26:24 +0100	[thread overview]
Message-ID: <ab0u4JS4Z7THrP6B@orbyte.nwl.cc> (raw)
In-Reply-To: <ab0tB2o90FukwQxU@strlen.de>

On Fri, Mar 20, 2026 at 12:18:31PM +0100, Florian Westphal wrote:
> Phil Sutter <phil@nwl.cc> wrote:
> > On Fri, Mar 20, 2026 at 11:17:00AM +0100, Phil Sutter wrote:
> > [...]
> > > A remark from a practical perspective: Florian's suggestion to dump the
> > > nat-type chains in their order with the dispatcher's priority value is
> > > super-easy to implement (just have to pass the priority value to
> > > nfnl_hook_dump_one() via parameter) and does not require adjustments in
> > > user space.
> > 
> > Famous last words. :(
> 
> diff --git a/src/mnl.c b/src/mnl.c
> index 4893af8322ae..b9efd3cfd3ce 100644
> --- a/src/mnl.c
> +++ b/src/mnl.c
> @@ -2520,7 +2520,7 @@ static void basehook_list_add_tail(struct basehook *b, struct list_head *head)
>                         continue;
>                 if (!basehook_eq(hook, b))
>                         continue;
> -               if (hook->prio < b->prio)
> +               if (hook->prio <= b->prio)
>                         continue;
>  
>                 list_add(&b->list, &hook->list);
> 
> ?

Sure, but <=nftables-1.1.6 will still get it wrong. Can we tolerate
that?

  reply	other threads:[~2026-03-20 11:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 15:32 [nf-next PATCH] netfilter: nfnetlink_hook: Dump nat type chains Phil Sutter
2026-03-19 16:04 ` Florian Westphal
2026-03-19 16:59   ` Phil Sutter
2026-03-19 17:06     ` Florian Westphal
2026-03-19 21:08       ` Phil Sutter
2026-03-20  0:24         ` Pablo Neira Ayuso
2026-03-20 10:17           ` Phil Sutter
2026-03-20 11:11             ` Phil Sutter
2026-03-20 11:18               ` Florian Westphal
2026-03-20 11:26                 ` Phil Sutter [this message]
2026-03-20 11:36                   ` Phil Sutter
2026-03-20 11:47                     ` Florian Westphal
2026-03-20 12:09                       ` Pablo Neira Ayuso
2026-03-20 12:27                         ` Phil Sutter
2026-03-20 11:45                   ` Florian Westphal
2026-03-20 11:46                   ` 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=ab0u4JS4Z7THrP6B@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox