From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@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>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] net/mlx5e: Avoid a hundred -Wflex-array-member-not-at-end warnings
Date: Tue, 4 Feb 2025 07:09:23 +0100 [thread overview]
Message-ID: <Z6GvE4su2/m9e+Ev@mev-dev.igk.intel.com> (raw)
In-Reply-To: <Z6GCJY8G9EzASrwQ@kspp>
On Tue, Feb 04, 2025 at 01:27:41PM +1030, Gustavo A. R. Silva wrote:
> -Wflex-array-member-not-at-end was introduced in GCC-14, and we are
> getting ready to enable it, globally.
>
> So, in order to avoid ending up with a flexible-array member in the
> middle of other structs, we use the `struct_group_tagged()` helper
> to create a new tagged `struct mlx5e_umr_wqe_hdr`. This structure
> groups together all the members of the flexible `struct mlx5e_umr_wqe`
> except the flexible array.
>
> As a result, the array is effectively separated from the rest of the
> members without modifying the memory layout of the flexible structure.
> We then change the type of the middle struct member currently causing
> trouble from `struct mlx5e_umr_wqe` to `struct mlx5e_umr_wqe_hdr`.
>
> We also want to ensure that when new members need to be added to the
> flexible structure, they are always included within the newly created
> tagged struct. For this, we use `static_assert()`. This ensures that the
> memory layout for both the flexible structure and the new tagged struct
> is the same after any changes.
>
> This approach avoids having to implement `struct mlx5e_umr_wqe_hdr` as
> a completely separate structure, thus preventing having to maintain two
> independent but basically identical structures, closing the door to
> potential bugs in the future.
>
> We also use `container_of()` whenever we need to retrieve a pointer to
> the flexible structure, through which we can access the flexible-array
> member, if necessary.
>
> So, with these changes, fix 124 of the following warnings:
>
> drivers/net/ethernet/mellanox/mlx5/core/en.h:664:48: warning: structure containing a flexible array member is not at the end of another structure [-Wflex-array-member-not-at-end]
>
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/en.h | 13 +++++++++----
> drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 4 +++-
> 2 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en.h b/drivers/net/ethernet/mellanox/mlx5/core/en.h
> index 979fc56205e1..c30c64eb346f 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en.h
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en.h
> @@ -233,15 +233,20 @@ struct mlx5e_rx_wqe_cyc {
> };
>
> struct mlx5e_umr_wqe {
> - struct mlx5_wqe_ctrl_seg ctrl;
> - struct mlx5_wqe_umr_ctrl_seg uctrl;
> - struct mlx5_mkey_seg mkc;
> + /* New members MUST be added within the struct_group() macro below. */
> + struct_group_tagged(mlx5e_umr_wqe_hdr, hdr,
> + struct mlx5_wqe_ctrl_seg ctrl;
> + struct mlx5_wqe_umr_ctrl_seg uctrl;
> + struct mlx5_mkey_seg mkc;
> + );
> union {
> DECLARE_FLEX_ARRAY(struct mlx5_mtt, inline_mtts);
> DECLARE_FLEX_ARRAY(struct mlx5_klm, inline_klms);
> DECLARE_FLEX_ARRAY(struct mlx5_ksm, inline_ksms);
> };
> };
> +static_assert(offsetof(struct mlx5e_umr_wqe, inline_mtts) == sizeof(struct mlx5e_umr_wqe_hdr),
> + "struct member likely outside of struct_group_tagged()");
>
> enum mlx5e_priv_flag {
> MLX5E_PFLAG_RX_CQE_BASED_MODER,
> @@ -660,7 +665,7 @@ struct mlx5e_rq {
> } wqe;
> struct {
> struct mlx5_wq_ll wq;
> - struct mlx5e_umr_wqe umr_wqe;
> + struct mlx5e_umr_wqe_hdr umr_wqe;
> struct mlx5e_mpw_info *info;
> mlx5e_fp_skb_from_cqe_mpwrq skb_from_cqe_mpwrq;
> __be32 umr_mkey_be;
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> index bd41b75d246e..4ff4ff2342cf 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> @@ -373,6 +373,8 @@ static void mlx5e_rq_shampo_hd_info_free(struct mlx5e_rq *rq)
>
> static int mlx5e_rq_alloc_mpwqe_info(struct mlx5e_rq *rq, int node)
> {
> + struct mlx5e_umr_wqe *umr_wqe =
> + container_of(&rq->mpwqe.umr_wqe, struct mlx5e_umr_wqe, hdr);
> int wq_sz = mlx5_wq_ll_get_size(&rq->mpwqe.wq);
> size_t alloc_size;
>
> @@ -393,7 +395,7 @@ static int mlx5e_rq_alloc_mpwqe_info(struct mlx5e_rq *rq, int node)
> bitmap_fill(wi->skip_release_bitmap, rq->mpwqe.pages_per_wqe);
> }
>
> - mlx5e_build_umr_wqe(rq, rq->icosq, &rq->mpwqe.umr_wqe);
> + mlx5e_build_umr_wqe(rq, rq->icosq, umr_wqe);
>
> return 0;
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> }
> --
> 2.43.0
next prev parent reply other threads:[~2025-02-04 6:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 2:57 [PATCH][next] net/mlx5e: Avoid a hundred -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-02-04 6:09 ` Michal Swiatkowski [this message]
2025-02-06 4:37 ` Gustavo A. R. Silva
2025-02-06 7:25 ` Tariq Toukan
2025-02-18 8:14 ` Gustavo A. R. Silva
2025-02-18 9:49 ` Tariq Toukan
2025-02-18 15:37 ` Andrew Lunn
2025-02-18 15:53 ` Tariq Toukan
2025-02-18 21:13 ` Jakub Kicinski
2025-02-19 12:14 ` Tariq Toukan
2025-02-20 1:46 ` Jakub Kicinski
2025-02-20 7:41 ` Tariq Toukan
2025-02-20 18:26 ` Jakub Kicinski
2025-02-20 21:49 ` Saeed Mahameed
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=Z6GvE4su2/m9e+Ev@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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