diff options
author | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-02-11 17:19:11 -0600 |
---|---|---|
committer | Mika Westerberg <mika.westerberg@linux.intel.com> | 2020-02-14 15:07:03 +0300 |
commit | c2a9fca17e4c021e526cc52b78e0f30105024b82 (patch) | |
tree | 9e6552f897af6326b6ed958595ef1e9263c6d26b /drivers/nvmem | |
parent | bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9 (diff) | |
download | linux-c2a9fca17e4c021e526cc52b78e0f30105024b82.tar.bz2 |
thunderbolt: eeprom: 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
inadvertenly introduced[3] to the codebase from now on.
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: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'drivers/nvmem')
0 files changed, 0 insertions, 0 deletions