diff options
| author | Gustavo A. R. Silva <gustavoars@kernel.org> | 2022-02-21 11:34:15 -0600 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2022-02-22 17:00:54 -0800 |
| commit | cc727b6418004e90e1fea04d70f95e97dcf45331 (patch) | |
| tree | 1c6b162adcd1d5df60fe3daa1f45a0824f9c9db2 /tools | |
| parent | 1054457006d4a14de4ae4132030e33d7eedaeba1 (diff) | |
| download | linux-cc727b6418004e90e1fea04d70f95e97dcf45331.tar.gz linux-cc727b6418004e90e1fea04d70f95e97dcf45331.tar.bz2 linux-cc727b6418004e90e1fea04d70f95e97dcf45331.zip | |
usbnet: gl620a: 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>
Link: https://lore.kernel.org/r/20220221173415.GA1149599@embeddedor
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions