From: Florian Fainelli <f.fainelli@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-stable <stable@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
linux-rdma@vger.kernel.org, lkft-triage@lists.linaro.org,
Sasha Levin <sashal@kernel.org>,
Leon Romanovsky <leonro@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: stable-rc: 6.1: mlx5: params.c:994:53: error: 'MLX5_IPSEC_CAP_CRYPTO' undeclared (first use in this function)
Date: Mon, 29 Jan 2024 20:25:42 -0800 [thread overview]
Message-ID: <8c178bd1-e0c9-4e29-9b63-dd298298bc7b@gmail.com> (raw)
In-Reply-To: <CA+G9fYs3_M9E3w+uWky5X1hEgoJU4e92ECqSywerqSkF8KVGvA@mail.gmail.com>
On 1/29/2024 6:52 PM, Naresh Kamboju wrote:
> On Mon, 29 Jan 2024 at 21:58, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> On Mon, Jan 29, 2024 at 09:17:31PM +0530, Naresh Kamboju wrote:
>>> Following build errors noticed on stable-rc linux-6.1.y for arm64.
>>>
>>> arm64:
>>> --------
>>> * build/gcc-13-lkftconfig
>>> * build/gcc-13-lkftconfig-kunit
>>> * build/clang-nightly-lkftconfig
>>> * build/clang-17-lkftconfig-no-kselftest-frag
>>> * build/gcc-13-lkftconfig-devicetree
>>> * build/clang-lkftconfig
>>> * build/gcc-13-lkftconfig-perf
>>>
>>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>>
>>> Build errors:
>>> ------
>>> drivers/net/ethernet/mellanox/mlx5/core/en/params.c: In function
>>> 'mlx5e_build_sq_param':
>>> drivers/net/ethernet/mellanox/mlx5/core/en/params.c:994:53: error:
>>> 'MLX5_IPSEC_CAP_CRYPTO' undeclared (first use in this function)
>>> 994 | (mlx5_ipsec_device_caps(mdev) &
>>> MLX5_IPSEC_CAP_CRYPTO);
>>> |
>>> ^~~~~~~~~~~~~~~~~~~~~
>>>
>>> Suspecting commit:
>>> net/mlx5e: Allow software parsing when IPsec crypto is enabled
>>> [ Upstream commit 20f5468a7988dedd94a57ba8acd65ebda6a59723 ]
>>
>> Something looks very odd here, as the proper .h file is being included,
>> AND this isn't a build failure on x86, so why is this only arm64 having
>> problems? What's causing this not to show up?
>
> As per the Daniel report on stable-rc review on 6.1, these build failures also
> reported on System/390.
The build failure is legitimate here since
drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.h guards all of
the definitions and enumerations under a CONFIG_MLX5_EN_IPSEC which is
not enabled in the build configuration that failed.
This is implicitly fixed upstream with
8c582ddfbb473c1d799c40b5140aed81278e2837 ("net/mlx5e: Handle hardware
IPsec limits events") which relocates the #ifdef CONFIG_MLX5_EN_IPSEC
below and allows the MLX5_IPSEC_CAP_CRYPTO enum value, amongst others to
be visible to code that is not guarded with CONFIG_MLX5_EN_IPSEC. This
specific commit does not apply cleanly to the stable-6.1 branch, so
maybe the best we can come up with is this targeted change that does the
same thing against 6.1:
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.h
b/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.h
index 16bcceec16c4..785f188148d8 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.h
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.h
@@ -34,7 +34,6 @@
#ifndef __MLX5E_IPSEC_H__
#define __MLX5E_IPSEC_H__
-#ifdef CONFIG_MLX5_EN_IPSEC
#include <linux/mlx5/device.h>
#include <net/xfrm.h>
@@ -146,6 +145,7 @@ struct mlx5e_ipsec_sa_entry {
struct mlx5e_ipsec_modify_state_work modify_work;
};
+#ifdef CONFIG_MLX5_EN_IPSEC
int mlx5e_ipsec_init(struct mlx5e_priv *priv);
void mlx5e_ipsec_cleanup(struct mlx5e_priv *priv);
void mlx5e_ipsec_build_netdev(struct mlx5e_priv *priv);
--
Florian
next prev parent reply other threads:[~2024-01-30 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 15:47 stable-rc: 6.1: mlx5: params.c:994:53: error: 'MLX5_IPSEC_CAP_CRYPTO' undeclared (first use in this function) Naresh Kamboju
2024-01-29 16:28 ` Greg Kroah-Hartman
2024-01-30 2:52 ` Naresh Kamboju
2024-01-30 4:25 ` Florian Fainelli [this message]
2024-01-30 7:14 ` Leon Romanovsky
2024-01-30 18:30 ` Greg Kroah-Hartman
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=8c178bd1-e0c9-4e29-9b63-dd298298bc7b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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