diff options
author | Gustavo A. R. Silva <gustavoars@kernel.org> | 2020-05-22 12:43:55 -0500 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2020-05-28 14:00:50 -0400 |
commit | 4541ea81edde6ce9a1d9be082489aca7e8e7e1dc (patch) | |
tree | cb1eaa4700c524584b2bd4dfae021679c823db4d /drivers/gpio/gpio-gpio-mm.c | |
parent | 6e20010a3acc41817daf69f801d8e9c34975223e (diff) | |
download | linux-stable-4541ea81edde6ce9a1d9be082489aca7e8e7e1dc.tar.gz linux-stable-4541ea81edde6ce9a1d9be082489aca7e8e7e1dc.tar.bz2 linux-stable-4541ea81edde6ce9a1d9be082489aca7e8e7e1dc.zip |
drm/[radeon|amdgpu]: Replace one-element array and use struct_size() helper
The current codebase makes use of one-element arrays in the following
form:
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);
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. So, replace
the one-element array with a flexible-array member.
Also, make use of the new struct_size() helper to properly calculate the
size of struct SISLANDS_SMC_SWSTATE.
This issue was found with the help of Coccinelle and, audited and fixed
_manually_.
[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 <gustavoars@kernel.org>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpio/gpio-gpio-mm.c')
0 files changed, 0 insertions, 0 deletions