aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/failed-syscalls-by-pid.py
diff options
context:
space:
mode:
authorPeter Ujfalusi <[email protected]>2022-07-12 15:23:56 +0300
committerMark Brown <[email protected]>2022-07-12 13:45:02 +0100
commit499cc881b09c8283ab5e75b0d6d21cb427722161 (patch)
treefc045af0537c792fc8fafb7c7dfa1508c5e138b7 /tools/perf/scripts/python/failed-syscalls-by-pid.py
parentacacd9eefd0def5a83244d88e5483b5f38ee7287 (diff)
ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot
It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same condition is present for IPC3. Reported-by: Kai Vehmanen <[email protected]> Signed-off-by: Peter Ujfalusi <[email protected]> Reviewed-by: Ranjani Sridharan <[email protected]> Reviewed-by: Pierre-Louis Bossart <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions