diff options
author | Gustavo A. R. Silva | 2020-01-16 16:03:27 -0600 |
---|---|---|
committer | Johan Hovold | 2020-01-17 11:44:23 +0100 |
commit | 50c3c5e1c1b000d6a321ffdc0003bc6b7ac0b0e5 (patch) | |
tree | efea0e6b4557ac18e8e1d99c38727283998bd85f /crypto/rsa.c | |
parent | e6421583953fd92eba1785f90b228d70345125d6 (diff) |
USB: serial: garmin_gps: Use flexible-array member
Old code in the kernel uses 1-byte and 0-byte arrays to indicate the
presence of a "variable length array":
struct something {
int length;
u8 data[1];
};
struct something *instance;
instance = kmalloc(sizeof(*instance) + size, GFP_KERNEL);
instance->length = size;
memcpy(instance->data, source, size);
There is also 0-byte arrays. Both cases pose confusion for things like
sizeof(), CONFIG_FORTIFY_SOURCE, etc.[1] Instead, the preferred mechanism
to declare variable-length types such as the one above is a flexible array
member[2] which need to be the last member of a structure and empty-sized:
struct something {
int stuff;
u8 data[];
};
Also, 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
unadvertenly introduced[3] to the codebase from now on.
[1] https://github.com/KSPP/linux/issues/21
[2] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
[3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour")
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Signed-off-by: Johan Hovold <johan@kernel.org>
Diffstat (limited to 'crypto/rsa.c')
0 files changed, 0 insertions, 0 deletions