[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250423070002.3dde704e@kernel.org>
Date: Wed, 23 Apr 2025 07:00:02 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Pablo Neira Ayuso <pablo@...filter.org>
Cc: netfilter-devel@...r.kernel.org, davem@...emloft.net,
netdev@...r.kernel.org, pabeni@...hat.com, edumazet@...gle.com,
fw@...len.de, horms@...nel.org
Subject: Re: [PATCH net-next 4/7] netfilter: Exclude LEGACY TABLES on
PREEMPT_RT.
On Tue, 22 Apr 2025 22:23:24 +0200 Pablo Neira Ayuso wrote:
> +config NETFILTER_LEGACY
> + bool "Netfilter legacy tables support"
> + depends on NETFILTER && !PREEMPT_RT
> + help
> + Say Y here if you still require support for legacy tables. This is
> + required by the legacy tools (iptables-legacy) and is not needed if
> + you use iptables over nftables (iptales-nft).
> + Legacy support is not limited to IP, it also includes EBTABLES and
> + ARPTABLES.
I think you need to adjust a bunch of existing config files.
Or make this somehow default to y when they are selected
instead of having them depend on the LEGACY feature.
All these failures are because netdev CI builds based on relevant
configs in tools/testing/selftests lost the netfilter modules:
https://netdev.bots.linux.dev/contest.html?branch=net-next-2025-04-23--12-00&pw-n=0&pass=0
Not sure if platform configs include netfilter but they may have
similar problem..
--
pw-bot: cr
Powered by blists - more mailing lists