diff options
| author | 2022-02-04 17:21:44 -0600 | |
|---|---|---|
| committer | 2022-02-05 15:28:10 +0000 | |
| commit | 76ad950c8fd7a4625908c679374f70d22272dfb3 (patch) | |
| tree | 23e610c4ebac522ee93ca4dc068e71b37d778432 /include/linux | |
| parent | Merge branch 'net-mana-next' (diff) | |
| download | linux-dev-76ad950c8fd7a4625908c679374f70d22272dfb3.tar.xz linux-dev-76ad950c8fd7a4625908c679374f70d22272dfb3.zip | |
bnx2x: Replace one-element array with flexible-array member
There is a regular need in the kernel to provide a way to declare having
a dynamically sized set of trailing elements in a structure. Kernel code
should always use “flexible array members”[1] for these cases. The older
style of one-element or zero-length arrays should no longer be used[2].
This helps with the ongoing efforts to globally enable -Warray-bounds
and get us closer to being able to tighten the FORTIFY_SOURCE routines
on memcpy().
This issue was found with the help of Coccinelle and audited and fixed,
manually.
[1] https://en.wikipedia.org/wiki/Flexible_array_member
[2] https://www.kernel.org/doc/html/v5.16/process/deprecated.html#zero-length-and-one-element-arrays
Link: https://github.com/KSPP/linux/issues/79
Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
