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 v2] netfilter: nf_tables: Introduce NFTA_RULE_ACTUAL_EXPR
Date: Thu, 27 Apr 2023 12:57:30 +0200 [thread overview]
Message-ID: <ZEpVGpY3QzUwAMia@orbyte.nwl.cc> (raw)
In-Reply-To: <ZEmCdMVboNu6dKiL@calendula>
Hi Pablo,
On Wed, Apr 26, 2023 at 09:58:44PM +0200, Pablo Neira Ayuso wrote:
[...]
> My proposal:
Thanks for returning to this. Your approach requires to define a minimum
version from which on forward-compat is guaranteed. I was trying to
avoid this requirement though so things would work for "unknown user
space".
Currently, the only offending extension is ebt_among since it doesn't
exist (and never did) in non-native form. If I implement among extension
parsing (even in non-functional form), my original approach would work.
This also means having a minimum version for full compat, but it affects
ebtables (actually, use of ebt_among) only.
Cheers, Phil
next prev parent reply other threads:[~2023-04-27 10:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 14:22 [nf-next PATCH v2] netfilter: nf_tables: Introduce NFTA_RULE_ACTUAL_EXPR Phil Sutter
2023-01-12 10:15 ` Phil Sutter
2023-01-12 11:06 ` Pablo Neira Ayuso
2023-01-12 12:02 ` Phil Sutter
2023-01-18 11:58 ` Pablo Neira Ayuso
2023-01-18 13:48 ` Phil Sutter
2023-02-02 21:31 ` Pablo Neira Ayuso
2023-02-03 13:48 ` Phil Sutter
2023-02-03 15:32 ` Pablo Neira Ayuso
2023-02-03 16:21 ` Phil Sutter
2023-02-04 9:41 ` Pablo Neira Ayuso
2023-02-04 21:00 ` Phil Sutter
2023-02-06 9:52 ` Pablo Neira Ayuso
2023-02-07 10:43 ` Pablo Neira Ayuso
2023-02-07 10:56 ` Phil Sutter
2023-02-16 10:55 ` Phil Sutter
2023-02-16 11:29 ` Pablo Neira Ayuso
2023-02-16 12:05 ` Phil Sutter
2023-04-26 19:58 ` Pablo Neira Ayuso
2023-04-27 10:57 ` Phil Sutter [this message]
2023-04-27 11:01 ` Pablo Neira Ayuso
2023-04-27 11:33 ` Phil Sutter
2023-04-27 13:07 ` Pablo Neira Ayuso
2023-04-27 22:45 ` Phil Sutter
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=ZEpVGpY3QzUwAMia@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).