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 13:27:33 +0100 [thread overview]
Message-ID: <ab09NRykeKil5ih9@orbyte.nwl.cc> (raw)
In-Reply-To: <ab047FS3MijyN_Ik@chamomile>
On Fri, Mar 20, 2026 at 01:09:16PM +0100, Pablo Neira Ayuso wrote:
> On Fri, Mar 20, 2026 at 12:47:23PM +0100, Florian Westphal wrote:
> > Phil Sutter <phil@nwl.cc> wrote:
> > > > Sure, but <=nftables-1.1.6 will still get it wrong. Can we tolerate
> > > > that?
> > >
> > > The kernel could dump them in reverse. :D
> >
> > WTF, no no no.
> >
> > The kernel is fine, this is a userspace bug.
>
> I think so too.
>
> One of the main use-cases for 'list hooks' is to display the order in
> which hooks are run.
Guys, you're obviously right! Took me a while to realize this behaviour
is not isolated to newly dumped nat-type chains with same prio, but
other chains may have same prio values as well. So: Fix for user space,
continue as planned in kernel space.
Thanks!
next prev parent reply other threads:[~2026-03-20 12:27 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
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 [this message]
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=ab09NRykeKil5ih9@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