summaryrefslogtreecommitdiffstats
path: root/drivers/nubus
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavoars@kernel.org>2021-08-10 16:07:41 -0500
committerMartin K. Petersen <martin.petersen@oracle.com>2021-08-17 22:28:39 -0400
commit5f492a7aa13b4ebf8ca85e818585394053065240 (patch)
tree3951bb134fb39260a45ea9e75e167b232dabf02e /drivers/nubus
parent0f99792c01d1d6d35b86e850e9ccadd98d6f3e0c (diff)
downloadlinux-stable-5f492a7aa13b4ebf8ca85e818585394053065240.tar.gz
linux-stable-5f492a7aa13b4ebf8ca85e818585394053065240.tar.bz2
linux-stable-5f492a7aa13b4ebf8ca85e818585394053065240.zip
scsi: smartpqi: 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]. Refactor the code a bit according to the use of a flexible-array member in struct pqi_event_config instead of a one-element array, and use the struct_size() helper. 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.10/process/deprecated.html#zero-length-and-one-element-arrays Link: https://github.com/KSPP/linux/issues/79 Link: https://github.com/KSPP/linux/issues/109 Link: https://lore.kernel.org/r/20210810210741.GA58765@embeddedor Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/nubus')
0 files changed, 0 insertions, 0 deletions