From: Saeed Mahameed <saeed@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
"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: Replace zero-length array with flexible-array member
Date: Tue, 10 Jan 2023 13:52:25 -0800 [thread overview]
Message-ID: <Y73eGayohIOnM+sp@x130> (raw)
In-Reply-To: <Y7zB7shx/u1zWrbj@work>
On 09 Jan 19:39, Gustavo A. R. Silva wrote:
>Zero-length arrays are deprecated[1] and we are moving towards
>adopting C99 flexible-array members instead. So, replace zero-length
>array declaration in struct mlx5e_flow_meter_aso_obj with flex-array
>member.
>
>This helps with the ongoing efforts to tighten the FORTIFY_SOURCE
>routines on memcpy() and help us make progress towards globally
>enabling -fstrict-flex-arrays=3 [2].
>
>Link: https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays [1]
>Link: https://gcc.gnu.org/pipermail/gcc-patches/2022-October/602902.html [2]
>Link: https://github.com/KSPP/linux/issues/78
>Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Applied to net-next-mlx5, Thanks!
next prev parent reply other threads:[~2023-01-10 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 1:39 [PATCH][next] net/mlx5e: Replace zero-length array with flexible-array member Gustavo A. R. Silva
2023-01-10 21:52 ` Saeed Mahameed [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-18 20:31 Gustavo A. R. Silva
2020-02-19 7:14 ` Leon Romanovsky
2020-02-19 20:00 ` Gustavo A. R. Silva
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=Y73eGayohIOnM+sp@x130 \
--to=saeed@kernel.org \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).