diff options
author | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-02-24 10:32:52 -0600 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-02-24 15:26:17 -0800 |
commit | f49b2759821e3af7c3740b52ca91053b16c91103 (patch) | |
tree | b05ada22b0dc60a17935a1e0a6ccaa25385479b9 /drivers/net/ethernet/netronome/nfp/bpf/fw.h | |
parent | 65dc2f1a44df01eab3c93b7ecdd3fb393f9e81a2 (diff) |
toshiba: Replace zero-length array with flexible-array member
The current codebase makes use of the zero-length array language
extension to the C90 standard, but the preferred mechanism to declare
variable-length types such as these ones is a flexible array member[1][2],
introduced in C99:
struct foo {
int stuff;
struct boo array[];
};
By making use of the mechanism above, we will get a compiler warning
in case the flexible array does not occur last in the structure, which
will help us prevent some kind of undefined behavior bugs from being
inadvertently introduced[3] to the codebase from now on.
Also, notice that, dynamic memory allocations won't be affected by
this change:
"Flexible array members have incomplete type, and so the sizeof operator
may not be applied. As a quirk of the original implementation of
zero-length arrays, sizeof evaluates to zero."[1]
This issue was found with the help of Coccinelle.
[1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
[2] https://github.com/KSPP/linux/issues/21
[3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour")
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/netronome/nfp/bpf/fw.h')
0 files changed, 0 insertions, 0 deletions