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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250630172237.03d08cfc@kernel.org>
Date: Mon, 30 Jun 2025 17:22:37 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
 netdev@...r.kernel.org, linux-kselftest@...r.kernel.org, Jamal Hadi Salim
 <jhs@...atatu.com>, Jiri Pirko <jiri@...nulli.us>, Shuah Khan
 <shuah@...nel.org>
Subject: Re: [PATCH net-next] selftests/tc-testing: Enable CONFIG_IP_SET

On Mon, 30 Jun 2025 14:50:24 -0700 Cong Wang wrote:
> On Mon, Jun 30, 2025 at 05:33:41PM +0200, Sebastian Andrzej Siewior wrote:
> > The config snippet specifies CONFIG_NET_EMATCH_IPSET. This option
> > depends on CONFIG_IP_SET.  
> 
> So it should be set automatically when running `make` ? IOW, why do we
> have to set it explicitly?

EMATCH_IPSET `depend`s on IP_SET not `select`s ...
I think the patch makes sense. Or do you see another symbol which
should get us IP_SET in the resulting config?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ