summaryrefslogtreecommitdiffstats
path: root/COPYING
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2020-02-18 14:31:14 -0600
committerLeon Romanovsky <leonro@mellanox.com>2020-02-19 09:13:10 +0200
commit339ffae598ed74a0220a92c9b8d1cecb2e9a0dc8 (patch)
tree339b66bb7dd03a4bc5842f61ad861de498819719 /COPYING
parentd8fab4815a371e8013e1a769c31da1bcaf618b01 (diff)
downloadlinux-339ffae598ed74a0220a92c9b8d1cecb2e9a0dc8.tar.gz
linux-339ffae598ed74a0220a92c9b8d1cecb2e9a0dc8.tar.bz2
linux-339ffae598ed74a0220a92c9b8d1cecb2e9a0dc8.zip
net/mlx5e: 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: Leon Romanovsky <leonro@mellanox.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions