aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorWill Deacon <[email protected]>2019-12-19 12:03:46 +0000
committerJoerg Roedel <[email protected]>2019-12-23 14:06:05 +0100
commit34debdca68efd5625a2fcea7df1a215591a01f80 (patch)
treea5e46ba5e75cb173a12e8e8e3e963371e2034ea5 /tools/perf/scripts/python/export-to-sqlite.py
parentb06c076ea96258f31eabd2987a14193883b3641e (diff)
iommu/arm-smmu: Prevent forced unbinding of Arm SMMU drivers
Forcefully unbinding the Arm SMMU drivers is a pretty dangerous operation, since it will likely lead to catastrophic failure for any DMA devices mastering through the SMMU being unbound. When the driver then attempts to "handle" the fatal faults, it's very easy to trip over dead data structures, leading to use-after-free. On John's machine, he reports that the machine was "unusable" due to loss of the storage controller following a forced unbind of the SMMUv3 driver: | # cd ./bus/platform/drivers/arm-smmu-v3 | # echo arm-smmu-v3.0.auto > unbind | hisi_sas_v2_hw HISI0162:01: CQE_AXI_W_ERR (0x800) found! | platform arm-smmu-v3.0.auto: CMD_SYNC timeout at 0x00000146 | [hwprod 0x00000146, hwcons 0x00000000] Prevent this forced unbinding of the drivers by setting "suppress_bind_attrs" to true. Link: https://lore.kernel.org/lkml/[email protected] Reported-by: John Garry <[email protected]> Signed-off-by: Will Deacon <[email protected]> Tested-by: John Garry <[email protected]> # smmu v3 Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Joerg Roedel <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions