diff options
author | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-03-23 16:58:49 -0500 |
---|---|---|
committer | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-04-18 15:44:55 -0500 |
commit | 312322722872324939f0d0347a6e41807c2d4c56 (patch) | |
tree | e4c15c3f9b3f8485bd6f931e47c851602d782897 | |
parent | 7856e9f12f1f59cc6abb25f92b336528d0660ebb (diff) | |
download | lwn-312322722872324939f0d0347a6e41807c2d4c56.tar.gz lwn-312322722872324939f0d0347a6e41807c2d4c56.zip |
lib: cpu_rmap: 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>
-rw-r--r-- | include/linux/cpu_rmap.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/cpu_rmap.h b/include/linux/cpu_rmap.h index 02edeafcb2bf..be8aea04d023 100644 --- a/include/linux/cpu_rmap.h +++ b/include/linux/cpu_rmap.h @@ -28,7 +28,7 @@ struct cpu_rmap { struct { u16 index; u16 dist; - } near[0]; + } near[]; }; #define CPU_RMAP_DIST_INF 0xffff |