public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jianbo Liu <jianbol@nvidia.com>
To: Arnd Bergmann <arnd@kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	"Leon Romanovsky" <leon@kernel.org>,
	Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Cosmin Ratiu <cratiu@nvidia.com>,
	"Raed Salem" <raeds@nvidia.com>, <netdev@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [net-next] net/mlx5e: fix ip6_dst_lookup link failure
Date: Fri, 6 Feb 2026 17:56:08 +0800	[thread overview]
Message-ID: <8da9781c-4b89-41cc-8810-8312ef7c2c81@nvidia.com> (raw)
In-Reply-To: <20260204130057.4107804-1-arnd@kernel.org>



On 2/4/2026 9:00 PM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> Changing mlx5 to call ip6_dst_lookup() means it now fails to link
> when IPv6 is a loadable module but ipsec support is built-in:
> 
> ipsec.c:(.text+0x1061): undefined reference to `ip6_dst_lookup'
> 
> Add a Kconfig dependency that removes avoids this configuration.
> 
> Fixes: e35d7da8dd9e ("net/mlx5e: Use ip6_dst_lookup instead of ipv6_dst_lookup_flow for MAC init")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>   drivers/net/ethernet/mellanox/mlx5/core/Kconfig | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/Kconfig b/drivers/net/ethernet/mellanox/mlx5/core/Kconfig
> index 9cf394c66939..c298efe93f97 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/Kconfig
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/Kconfig
> @@ -154,6 +154,7 @@ config MLX5_EN_IPSEC
>   	depends on MLX5_CORE_EN
>   	depends on XFRM_OFFLOAD
>   	depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD
> +	depends on IPV6!=m || MLX5_CORE=m

Thanks for the fix.
I received a report for this same error here: 
https://lore.kernel.org/oe-kbuild-all/202512261850.P5Jp5BSz-lkp@intel.com/

We were about to send a fix ourselves, it is to simply add:
   depends on IPV6 || !IPV6
Is there a specific reason to prefer "depends on IPV6!=m || 
MLX5_CORE=m"? To me, the IPV6 || !IPV6 syntax seems a bit cleaner.

Thanks!
Jianbo

>   	help
>   	  Build support for IPsec cryptography-offload acceleration in the NIC.
>   


  parent reply	other threads:[~2026-02-06  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 13:00 [PATCH] [net-next] net/mlx5e: fix ip6_dst_lookup link failure Arnd Bergmann
2026-02-06  2:09 ` Jakub Kicinski
2026-02-06  9:56 ` Jianbo Liu [this message]
2026-02-06 10:00   ` [PATCH] " Arnd Bergmann
2026-02-06 11:45     ` Jianbo Liu

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=8da9781c-4b89-41cc-8810-8312ef7c2c81@nvidia.com \
    --to=jianbol@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=raeds@nvidia.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox