aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorGustavo A. R. Silva <[email protected]>2022-02-04 17:29:44 -0600
committerGreg Kroah-Hartman <[email protected]>2022-02-08 10:33:45 +0100
commit20198dd98cb5eb32e87f9370d20717b460c75d4a (patch)
tree05809f2eb1494bbd41dab9d4c601ef12137da966 /tools/perf/scripts/python/export-to-sqlite.py
parent1091a8737b9ea32960d73bedb4d30c34aace5f9a (diff)
staging: gdm724x: Replace one-element array with flexible-array member
There is a regular need in the kernel to provide a way to declare having a dynamically sized set of trailing elements in a structure. Kernel code should always use “flexible array members”[1] for these cases. The older style of one-element or zero-length arrays should no longer be used[2]. This helps with the ongoing efforts to globally enable -Warray-bounds and get us closer to being able to tighten the FORTIFY_SOURCE routines on memcpy(). This issue was found with the help of Coccinelle and audited and fixed, manually. [1] https://en.wikipedia.org/wiki/Flexible_array_member [2] https://www.kernel.org/doc/html/v5.16/process/deprecated.html#zero-length-and-one-element-arrays Link: https://github.com/KSPP/linux/issues/79 Reviewed-by: Dan Carpenter <[email protected]> Signed-off-by: Gustavo A. R. Silva <[email protected]> Link: https://lore.kernel.org/r/20220204232944.GA454945@embeddedor Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions