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: [libnftnl PATCH] utils: Drop asterisk from end of NFTA_DEVICE_PREFIX strings
Date: Wed, 15 Oct 2025 22:08:47 +0200 [thread overview]
Message-ID: <aO__T5yX3xkD0djO@orbyte.nwl.cc> (raw)
In-Reply-To: <aO7PyNgUnGxg7qHt@calendula>
On Wed, Oct 15, 2025 at 12:33:44AM +0200, Pablo Neira Ayuso wrote:
> On Wed, Oct 08, 2025 at 12:05:53AM +0200, Phil Sutter wrote:
> > Hi Pablo,
> >
> > On Tue, Oct 07, 2025 at 11:42:05PM +0200, Pablo Neira Ayuso wrote:
> > > On Tue, Oct 07, 2025 at 05:58:26PM +0200, Phil Sutter wrote:
> > > > The asterisk left in place becomes part of the prefix by accident and is thus
> > > > both included when matching interface names as well as dumped back to user
> > > > space.
> > > >
> > > > Fixes: f30eae26d813e ("utils: Add helpers for interface name wildcards")
> > > > Signed-off-by: Phil Sutter <phil@nwl.cc>
> > > > ---
> > > > This code is currently unused by nftables at least since it builds the
> > > > netlink message itself.
> > >
> > > This was moved to nftables, and no release was made to include it?
> > > Would it possible to remove it from libnftnl?
> >
> > The code layout is a bit inconsistent in this regard: While nftables
> > does the serialization itself (to record offsets for extack), it relies
> > upon libnftnl to perform the deserialization. Therefore parts of the
> > wildcard interface feature will have to be spread over the two projects.
> > And since this is the case, I decided to keep libnftnl's serialization
> > code "maintained" in this regard, i.e. enable it to perform the netlink
> > message building for wildcard interface names as well even though there
> > is no known user for it.
> >
> > I'd prefer to keep it, also because I see us eventually returning to
> > libnftnl's serialization code once there is a mechanism to extract the
> > offsets for extack. You have the last word though (as always)! :)
>
> LGTM, thanks for explaining.
Patch applied, thanks!
prev parent reply other threads:[~2025-10-15 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 15:58 [libnftnl PATCH] utils: Drop asterisk from end of NFTA_DEVICE_PREFIX strings Phil Sutter
2025-10-07 21:42 ` Pablo Neira Ayuso
2025-10-07 22:05 ` Phil Sutter
2025-10-14 22:33 ` Pablo Neira Ayuso
2025-10-15 20:08 ` Phil Sutter [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=aO__T5yX3xkD0djO@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;
as well as URLs for NNTP newsgroup(s).