diff options
author | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-02-25 01:18:26 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-02-27 01:43:09 +0100 |
commit | d1c73cbdf9d3f6181a50398568372ef41b1f485c (patch) | |
tree | 0b938757becd55e3914f653e6f69aa35e8bf3626 /fs/sysfs | |
parent | net: marvell: Replace zero-length array with flexible-array member (diff) | |
download | linux-d1c73cbdf9d3f6181a50398568372ef41b1f485c.tar.xz linux-d1c73cbdf9d3f6181a50398568372ef41b1f485c.zip |
net: cisco: 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]
Lastly, fix the following checkpatch warning:
CHECK: Prefer kernel type 'u32' over 'u_int32_t'
#61: FILE: drivers/net/ethernet/cisco/enic/vnic_devcmd.h:653:
+ u_int32_t val[];
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 'fs/sysfs')
0 files changed, 0 insertions, 0 deletions