summaryrefslogtreecommitdiffstats
path: root/scripts/checkpatch.pl
diff options
context:
space:
mode:
authorLucas Segarra Fernandez <lucas.segarra.fernandez@intel.com>2024-04-16 12:33:37 +0200
committerHerbert Xu <herbert@gondor.apana.org.au>2024-04-26 17:26:09 +0800
commit483fd65ce29317044d1d00757e3fd23503b6b04c (patch)
tree864a712df930e1dae8ae8d96a1d950170a1a5915 /scripts/checkpatch.pl
parent23e4099bdc3c8381992f9eb975c79196d6755210 (diff)
downloadlinux-stable-483fd65ce29317044d1d00757e3fd23503b6b04c.tar.gz
linux-stable-483fd65ce29317044d1d00757e3fd23503b6b04c.tar.bz2
linux-stable-483fd65ce29317044d1d00757e3fd23503b6b04c.zip
crypto: qat - validate slices count returned by FW
The function adf_send_admin_tl_start() enables the telemetry (TL) feature on a QAT device by sending the ICP_QAT_FW_TL_START message to the firmware. This triggers the FW to start writing TL data to a DMA buffer in memory and returns an array containing the number of accelerators of each type (slices) supported by this HW. The pointer to this array is stored in the adf_tl_hw_data data structure called slice_cnt. The array slice_cnt is then used in the function tl_print_dev_data() to report in debugfs only statistics about the supported accelerators. An incorrect value of the elements in slice_cnt might lead to an out of bounds memory read. At the moment, there isn't an implementation of FW that returns a wrong value, but for robustness validate the slice count array returned by FW. Fixes: 69e7649f7cc2 ("crypto: qat - add support for device telemetry") Signed-off-by: Lucas Segarra Fernandez <lucas.segarra.fernandez@intel.com> Reviewed-by: Damian Muszynski <damian.muszynski@intel.com> Reviewed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'scripts/checkpatch.pl')
0 files changed, 0 insertions, 0 deletions