From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 94F90C77B61 for ; Thu, 27 Apr 2023 11:02:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243647AbjD0LCC (ORCPT ); Thu, 27 Apr 2023 07:02:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52578 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243304AbjD0LCB (ORCPT ); Thu, 27 Apr 2023 07:02:01 -0400 Received: from mail.netfilter.org (mail.netfilter.org [217.70.188.207]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 078854C09 for ; Thu, 27 Apr 2023 04:01:59 -0700 (PDT) Date: Thu, 27 Apr 2023 13:01:55 +0200 From: Pablo Neira Ayuso To: Phil Sutter , Florian Westphal , netfilter-devel@vger.kernel.org Subject: Re: [nf-next PATCH v2] netfilter: nf_tables: Introduce NFTA_RULE_ACTUAL_EXPR Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org On Thu, Apr 27, 2023 at 12:57:30PM +0200, Phil Sutter wrote: > 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". You also require a kernel that supports your approach. > 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. Yes, but this is fully user data, kernel really does not need to do anything with this alternative representation, which is what I do not like from you proposal. I really think userdata is the place to deal with this.