diff options
author | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-02-11 15:08:22 -0600 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-02-11 14:03:19 -0800 |
commit | 6736041f9606f195339cacb4bcce232f1a2a1ed3 (patch) | |
tree | 790752293ed46908735f3667a45836c967ec19ce /Kbuild | |
parent | d0cff8adce1370c03ddb2ccb4d8c2921e00181c4 (diff) | |
download | linux-6736041f9606f195339cacb4bcce232f1a2a1ed3.tar.gz linux-6736041f9606f195339cacb4bcce232f1a2a1ed3.tar.bz2 linux-6736041f9606f195339cacb4bcce232f1a2a1ed3.zip |
mei: bus: 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>
Link: https://lore.kernel.org/r/20200211210822.GA31368@embeddedor
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions