summaryrefslogtreecommitdiffstats
path: root/certs/system_keyring.c
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2019-08-29 12:29:16 -0500
committerMimi Zohar <zohar@linux.ibm.com>2019-08-29 14:23:30 -0400
commit2a7f0e53daf29ca6dc9fbe2a27158f13474ec1b5 (patch)
treee4abde280e962ea1da9bc6f5acf3400ed2d269e5 /certs/system_keyring.c
parentfa5b57175364431245b006c2afcbf94dc2b15400 (diff)
downloadlinux-2a7f0e53daf29ca6dc9fbe2a27158f13474ec1b5.tar.gz
linux-2a7f0e53daf29ca6dc9fbe2a27158f13474ec1b5.tar.bz2
linux-2a7f0e53daf29ca6dc9fbe2a27158f13474ec1b5.zip
ima: ima_api: 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 ima_template_entry { ... struct ima_field_data template_data[0]; /* template related data */ }; instance = kzalloc(sizeof(struct ima_template_entry) + count * sizeof(struct ima_field_data), GFP_NOFS); 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_NOFS); This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'certs/system_keyring.c')
0 files changed, 0 insertions, 0 deletions