diff options
author | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-02-12 13:37:00 -0600 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-02-12 12:07:12 -0800 |
commit | 00d963abcb92e9e3192036f83f5c3f964b19141a (patch) | |
tree | f89c3c9a9b7f6a34b3a2b9184e225b480ee69d34 /drivers/tty/n_gsm.c | |
parent | 57b76faf1d7860f070a1ee2d0b7eccd9f37ecc55 (diff) | |
download | kernel_replicant_linux-00d963abcb92e9e3192036f83f5c3f964b19141a.tar.gz kernel_replicant_linux-00d963abcb92e9e3192036f83f5c3f964b19141a.tar.bz2 kernel_replicant_linux-00d963abcb92e9e3192036f83f5c3f964b19141a.zip |
tty/serial: 8250_exar: 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.
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>
Link: https://lore.kernel.org/r/20200212193700.GA29715@embeddedor
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/tty/n_gsm.c')
0 files changed, 0 insertions, 0 deletions