From: Florian Westphal <fw@strlen.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>,
coreteam@netfilter.org,
"netdev-driver-reviewers@vger.kernel.org"
<netdev-driver-reviewers@vger.kernel.org>,
Hangbin Liu <liuhangbin@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [netfilter-core] [ANN] net-next is OPEN
Date: Thu, 25 Jan 2024 09:52:11 +0100 [thread overview]
Message-ID: <20240125085211.GE31645@breakpoint.cc> (raw)
In-Reply-To: <20240124210724.2b0e08ff@kernel.org>
Jakub Kicinski <kuba@kernel.org> wrote:
> On Wed, 24 Jan 2024 12:13:43 -0800 Jakub Kicinski wrote:
> > > if that is the nftables backend, it might be also that .config is
> > > missing CONFIG_NF_TABLES and CONFIG_NFT_COMPAT there, among other
> > > options.
> >
> > FWIW full config:
> >
> > https://netdev-2.bots.linux.dev/vmksft-net-mp/results/435321/config
> >
> > CONFIG_NFT_COMPAT was indeed missing! Let's see how it fares with it enabled.
>
> NFT_COMPAT fixed a lot! One remaining warning comes from using
> -m length. Which NFT config do we need for that one?
CONFIG_NETFILTER_XT_MATCH_LENGTH=m|y
next prev parent reply other threads:[~2024-01-25 8:52 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 17:16 [ANN] net-next is OPEN Jakub Kicinski
2024-01-22 20:54 ` Simon Horman
2024-01-23 8:45 ` Hangbin Liu
2024-01-23 15:20 ` Jakub Kicinski
2024-01-23 16:51 ` David Ahern
2024-01-23 21:39 ` Jakub Kicinski
2024-01-24 5:20 ` David Ahern
2024-01-24 8:22 ` Paolo Abeni
2024-01-24 15:07 ` Jakub Kicinski
2024-01-24 16:19 ` Jakub Kicinski
2024-01-24 16:35 ` David Ahern
2024-01-24 16:59 ` Jakub Kicinski
2024-01-24 21:48 ` David Ahern
2024-01-27 0:56 ` David Ahern
2024-01-27 1:13 ` Jakub Kicinski
2024-01-28 4:26 ` David Ahern
2024-01-29 9:23 ` Paolo Abeni
2024-01-29 15:03 ` Jakub Kicinski
2024-01-29 15:32 ` David Ahern
2024-01-29 16:53 ` Jakub Kicinski
2024-01-24 15:59 ` Willem de Bruijn
2024-01-24 16:22 ` Jakub Kicinski
2024-01-24 17:01 ` Jakub Kicinski
2024-01-24 18:35 ` Matthieu Baerts
2024-01-24 19:00 ` Jakub Kicinski
2024-01-24 19:18 ` [netfilter-core] " Pablo Neira Ayuso
2024-02-06 18:31 ` Matthieu Baerts
2024-02-07 9:49 ` Pablo Neira Ayuso
2024-02-07 11:33 ` Matthieu Baerts
2024-02-16 15:38 ` Pablo Neira Ayuso
2024-02-16 15:51 ` Matthieu Baerts
2024-01-24 19:16 ` Pablo Neira Ayuso
2024-01-24 19:40 ` Jakub Kicinski
2024-01-24 20:02 ` Pablo Neira Ayuso
2024-01-24 20:13 ` Jakub Kicinski
2024-01-25 5:07 ` Jakub Kicinski
2024-01-25 8:52 ` Florian Westphal [this message]
2024-01-25 17:30 ` Jakub Kicinski
2024-01-25 9:29 ` Pablo Neira Ayuso
2024-01-25 17:34 ` Jakub Kicinski
2024-01-24 17:42 ` Willem de Bruijn
2024-01-24 17:49 ` Jakub Kicinski
2024-01-24 18:23 ` Willem de Bruijn
2024-01-24 18:31 ` Paolo Abeni
2024-01-23 9:55 ` Petr Machata
2024-01-23 12:42 ` Matthias May
2024-01-23 13:38 ` Petr Machata
2024-01-23 15:30 ` Jakub Kicinski
2024-01-23 16:05 ` Petr Machata
2024-01-23 16:33 ` Jakub Kicinski
2024-01-23 15:34 ` Jakub Kicinski
2024-01-23 17:04 ` Petr Machata
2024-01-23 17:38 ` Jakub Kicinski
2024-01-24 11:06 ` Petr Machata
2024-01-29 12:43 ` Ido Schimmel
2024-01-29 12:46 ` Ido Schimmel
2024-01-29 15:00 ` Jakub Kicinski
2024-01-29 17:00 ` Ido Schimmel
2024-01-29 17:18 ` Jakub Kicinski
2024-01-31 13:23 ` Ido Schimmel
2024-01-31 14:16 ` Heiner Kallweit
2024-01-31 16:01 ` [TEST] bridge tests (was: net-next is OPEN) Jakub Kicinski
2024-02-01 13:46 ` Ido Schimmel
2024-02-01 15:30 ` Jakub Kicinski
2024-02-02 0:16 ` Jakub Kicinski
2024-02-08 16:21 ` Ido Schimmel
2024-02-08 17:26 ` Jakub Kicinski
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=20240125085211.GE31645@breakpoint.cc \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=willemdebruijn.kernel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.