summaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth/bfusb.c
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2020-02-26 17:02:27 -0600
committerMarcel Holtmann <marcel@holtmann.org>2020-02-28 08:30:02 +0100
commita7e454542bf8d57c75f59e7e7326c21db3d0bb3f (patch)
tree668c086fa84b889902a48b81cb10b13ed42a2436 /drivers/bluetooth/bfusb.c
parenteed467b517e8c6987e3f227758ff3e67c889e17b (diff)
downloadlinux-a7e454542bf8d57c75f59e7e7326c21db3d0bb3f.tar.bz2
Bluetooth: 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: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth/bfusb.c')
0 files changed, 0 insertions, 0 deletions