summaryrefslogtreecommitdiff
path: root/drivers/mmc/host/cqhci.c
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2020-02-27 01:31:25 +0300
committerUlf Hansson <ulf.hansson@linaro.org>2020-03-24 16:39:45 +0300
commit1a91a36aba9c232c73e4a5fce038147f5d29e566 (patch)
tree556ba35f35e808f13f5f51cc08f47c0a2b2b5d2c /drivers/mmc/host/cqhci.c
parentea21e9b2b33fd06c131415cc66ca5499ab2aef5f (diff)
downloadlinux-1a91a36aba9c232c73e4a5fce038147f5d29e566.tar.xz
mmc: 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> Acked-by: Adrian Hunter <adrian.hunter@intel.com> Link: https://lore.kernel.org/r/20200226223125.GA20630@embeddedor Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'drivers/mmc/host/cqhci.c')
0 files changed, 0 insertions, 0 deletions