summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorSara Sharon <sara.sharon@intel.com>2016-06-09 17:19:35 +0300
committerLuca Coelho <luciano.coelho@intel.com>2016-07-06 09:40:33 +0300
commitd5d0689aefc59c6a5352ca25d7e6d47d03f543ce (patch)
tree184846293e4c60361b7ac278db44665957ee8a9b /tools/perf/scripts/python/call-graph-from-postgresql.py
parent54f315cb082bf98290575e858d1e0274bb0eebe0 (diff)
iwlwifi: pcie: fix access to scratch buffer
This fixes a pretty ancient bug that hasn't manifested itself until now. The scratchbuf for command queue is allocated only for 32 slots but is accessed with the queue write pointer - which can be up to 256. Since the scratch buf size was 16 and there are up to 256 TFDs we never passed a page boundary when accessing the scratch buffer, but when attempting to increase the size of the scratch buffer a panic was quick to follow when trying to access the address resulted in a page boundary. Signed-off-by: Sara Sharon <sara.sharon@intel.com> Fixes: 38c0f334b359 ("iwlwifi: use coherent DMA memory for command header") Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions