[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aLY0hh8aBWJpluMI@strlen.de>
Date: Tue, 2 Sep 2025 02:04:22 +0200
From: Florian Westphal <fw@...len.de>
To: Pablo Neira Ayuso <pablo@...filter.org>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
Paolo Abeni <pabeni@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, netfilter-devel@...r.kernel.org
Subject: Re: [PATCH net-next 5/8] netfilter: nf_tables: Introduce
NFTA_DEVICE_PREFIX
Pablo Neira Ayuso <pablo@...filter.org> wrote:
> On Mon, Sep 01, 2025 at 01:46:02PM -0700, Jakub Kicinski wrote:
> > Why is this not targeting net? The sooner we adjust the uAPI the better.
I considered it a new feature rather than a bug fix:
Userspace can't rely on the existing api because kernels before
6.16 don't special-case the names provided, and nftables doesn't
make use of the 6.16 "accident" (the attempt to re-use the existing
device name attribute for this).
The corresponding userspace changes (v4 uses the new attribute)
haven't been merged yet.
But sure, getting rid of the "accident" faster makes sense,
thanks for suggesting this.
> I think there were doubts that was possible at this stage.
> But I agree, it is a bit late but better fix it there.
Alright, I'll send a new nf-next PR with this one dropped in a few hours
and a separate nf.git PR with this patch included.
If you prefer to just apply this series sand this patch that worls for
me too, I'll just follow this changesets' patchwork state.
Powered by blists - more mailing lists