Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp3273805pxp; Tue, 8 Mar 2022 10:51:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJx4Yzu8wKsfnGBRUVcg2ocugIpLwA6ZD7SOd0ZAcMsorbIfVRdd5g4/fvtFsqGz2RMw3RQ1 X-Received: by 2002:a17:907:94cb:b0:6da:97ec:3231 with SMTP id dn11-20020a17090794cb00b006da97ec3231mr14710173ejc.438.1646765462367; Tue, 08 Mar 2022 10:51:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646765462; cv=none; d=google.com; s=arc-20160816; b=u1KaXCygowCEjjR7B8rbNmc7EfWwFd7jItiZNHd0ugHcPllt9PeVTcHpaoUfcCTmgZ /8himCtWDFjQmCAJ4329DYx7hYNPZ64HdAHWInY7iR2HdyvV4lD5CZmzujN/PZ2a/ZH9 wM1qS9TvvnCiHVhvFx+kUjZ9zhV/UFVyhBR5j6N8JLdk5NUGXW5aHUp4HAwiYbP2kOWV ACwglyCQ2mkma1JMdB+uJl6cOLbcy3pWDZsUwSIIAQdOrcqs4ze3ZFJ1nWGBJjbNlw4T EqkvfP0BCaBmVdrnCzkxY8gdNxdhKFCL7d+ZhnBXbH13wqMPrGo2N4qCBeiAcF99x1YY BJXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=IfP4fjOD/Y64pId5d9oFQhRi2NdY2D3sFBR4lkA6mAQ=; b=Hf+VU7wkeZGzCEgp1ZH/NQXiuJ+Yt3ntIhBmNyg9S1zkfO1zttd6JG1bMEAS2g3o/o EuYXT8EVkIMdEoDCPLbQ2GCytVPanlXcBzAQS+TAl6emmODShyJ/9F3S16yga4ppK7Zg cVq3L1uGqemlCFH9uYNkxCF8/8ZLYJPjT/uqqP3KIujNEHjCZJNysaNRFgPa8yLGPRSa SHw2eHa+vum62MjqjJzToMtitsyGV81/GcALQ16BACc8OaT8QPK5qCobprKgyY/3qpxI LUaADnTVnTtAOL6NuAC36oEJn+tW+3QwpXcLEHusi52CzrX/WY3dcOZ78LwdXR9KdRSW VyLw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id jz16-20020a170906bb1000b006d1111257e1si9830367ejb.538.2022.03.08.10.50.37; Tue, 08 Mar 2022 10:51:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243725AbiCGVzR (ORCPT + 99 others); Mon, 7 Mar 2022 16:55:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33452 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243959AbiCGVzO (ORCPT ); Mon, 7 Mar 2022 16:55:14 -0500 Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc [IPv6:2a0a:51c0:0:12e:520::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E00227E0A8; Mon, 7 Mar 2022 13:54:18 -0800 (PST) Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.92) (envelope-from ) id 1nRLIy-0000vI-P4; Mon, 07 Mar 2022 22:54:12 +0100 Date: Mon, 7 Mar 2022 22:54:12 +0100 From: Florian Westphal To: Tom Rix Cc: Florian Westphal , pablo@netfilter.org, kadlec@netfilter.org, davem@davemloft.net, kuba@kernel.org, netfilter-devel@vger.kernel.org, coreteam@netfilter.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] netfilter: conditionally use ct and ctinfo Message-ID: <20220307215412.GA1822@breakpoint.cc> References: <20220305180853.696640-1-trix@redhat.com> <20220307124652.GB21350@breakpoint.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Tom Rix wrote: > > On 3/7/22 4:46 AM, Florian Westphal wrote: > > trix@redhat.com wrote: > > > From: Tom Rix > > > > > > The setting ct and ctinfo are controlled by > > > CONF_NF_CONNTRACK. So their use should also > > > be controlled. > > Any reason for this change? > > Define and use are connected. Doing something to one without doing something > to the other doesn't make sense. We often rely on compiler to remove branches that always evaluate to false, just like in this case. > Could removing the CONF_NF_CONNTRACK be done for the define side ? Doubt it. Looking at git history it avoids build breakage.