netdev - Re: [PATCH net-next 4/7] netfilter: Exclude LEGACY TABLES on PREEMPT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aAlVRq-ol-3jj1ml@calendula>
Date: Wed, 23 Apr 2025 23:01:58 +0200
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Florian Westphal <fw@...len.de>
Cc: Jakub Kicinski <kuba@...nel.org>, netfilter-devel@...r.kernel.org,
	davem@...emloft.net, netdev@...r.kernel.org, pabeni@...hat.com,
	edumazet@...gle.com, horms@...nel.org
Subject: Re: [PATCH net-next 4/7] netfilter: Exclude LEGACY TABLES on
 PREEMPT_RT.

Hi Florian,

On Wed, Apr 23, 2025 at 04:49:14PM +0200, Florian Westphal wrote:
> Florian Westphal <fw@...len.de> wrote:
> > I can have a look, likely there needs to a a patch before this one
> > that adds a few explicit CONFIG_ entries rather than replying on
> > implicit =y|m.
> 
> Pablo, whats the test suite expectation?
> 
> The netfilter tests pass when iptables is iptables-nft, but not
> when iptables is iptables-legacy.
> 
> I can either patch them and replace iptables with iptables-nft
> everywhere or I an update config so that iptables-legacy works too.
> 
> Unless you feel different, I will go with b) and add the needed
> legacy config options.

b) is fine with me.

> net tests are a different issue, they fail regardless of iptables-nft or
> legacy, looking at that now.

Thanks.