summaryrefslogtreecommitdiffstats
path: root/arch/arm/configs/nuc960_defconfig
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2019-03-08 01:29:47 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2019-03-08 03:32:02 +0100
commit9abdb50cda0ffe33bbb2e40cbad97b32fb7ff892 (patch)
tree698fa4965e0e92e94263fdaea28b3f9327d7612c /arch/arm/configs/nuc960_defconfig
parentsysctl: handle overflow for file-max (diff)
downloadlinux-9abdb50cda0ffe33bbb2e40cbad97b32fb7ff892.tar.xz
linux-9abdb50cda0ffe33bbb2e40cbad97b32fb7ff892.zip
kernel/gcov/gcc_3_4.c: use struct_size() in kzalloc()
One of the more common cases of allocation size calculations is finding the size of a structure that has a zero-sized array at the end, along with memory for some number of elements for that array. For example: struct foo { int stuff; void *entry[]; }; instance = kzalloc(sizeof(struct foo) + sizeof(void *) * count, GFP_KERNEL); Instead of leaving these open-coded and prone to type mistakes, we can now use the new struct_size() helper: instance = kzalloc(struct_size(instance, entry, count), GFP_KERNEL); This code was detected with the help of Coccinelle. Link: http://lkml.kernel.org/r/20190109172445.GA15908@embeddedor Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com> Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/arm/configs/nuc960_defconfig')
0 files changed, 0 insertions, 0 deletions