summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2017-01-04 14:09:41 +0300
committerKalle Valo <kvalo@codeaurora.org>2017-01-17 14:56:35 +0300
commit77c0d0cd10e793989d1e8b835a9a09694182cb39 (patch)
tree185e6832afaa053e5bab14533a9adbdfadac728d /tools/perf/scripts/python/export-to-postgresql.py
parent0e8edb9aed03892844713bb76a8e1d2d138f3175 (diff)
downloadlinux-77c0d0cd10e793989d1e8b835a9a09694182cb39.tar.xz
brcmfmac: avoid writing channel out of allocated array
Our code was assigning number of channels to the index variable by default. If firmware reported channel we didn't predict this would result in using that initial index value and writing out of array. This never happened so far (we got a complete list of supported channels) but it means possible memory corruption so we should handle it anyway. This patch simply detects unexpected channel and ignores it. As we don't try to create new entry now, it's also safe to drop hw_value and center_freq assignment. For known channels we have these set anyway. I decided to fix this issue by assigning NULL or a target channel to the channel variable. This was one of possible ways, I prefefred this one as it also avoids using channel[index] over and over. Fixes: 58de92d2f95e ("brcmfmac: use static superset of channels for wiphy bands") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions