diff options
| author | Mark Brown <broonie@kernel.org> | 2022-07-12 21:21:42 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2022-07-12 21:21:42 +0300 |
| commit | 501935dae855a469d7529500c450c550acc6e633 (patch) | |
| tree | bbfee05cd874143569f53545c83fc34cbc4c00e6 /tools/perf/scripts/python/arm-cs-trace-disasm.py | |
| parent | 274a3e6f98682ccad508a108312cfb5fb7c7553a (diff) | |
| parent | 1549a69b89b7e5b1b830da897529344766728a4b (diff) | |
| download | linux-501935dae855a469d7529500c450c550acc6e633.tar.xz | |
ASoC: SOF: Intel: Do not process IPC reply before firmware boot
Merge series from Peter Ujfalusi <peter.ujfalusi@linux.intel.com>:
By mistake a developer managed to create a 'corrupted' IPC4 firmware image which
loaded fine to the DSP and after boot it sent an IPC reply before we would have
received the FW_READY message.
It turned out that the image was an IPC3 firmware and the IPC reply was the IPC3
FW_READY notification message which got understood as an IPC4 reply message due
to the difference between the two IPC mechanism.
This caused a NULL pointer dereference since the reply memory will be allocated
after the FW_READY message.
To make sure this will not bite again, skip any spurious reply messages before
the FW_READY.
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions