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

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. :(

In fact, user space calls basehook_list_add_tail() for each received
hook message which (contrary to its name) inserts sorted by ascending
priority value. It does this by skipping as long as the cursor's
priority is lower than the new element's, i.e. hooks with same priority
value are inserted in reverse order than received. This is a no-go since
ordering matters, right?

Cheers, Phil

  reply	other threads:[~2026-03-20 11:11 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 [this message]
2026-03-20 11:18               ` Florian Westphal
2026-03-20 11:26                 ` Phil Sutter
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=ab0rbTfE7LWIk7f-@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