diff options
| author | Will Deacon | 2018-07-25 16:58:43 +0200 |
|---|---|---|
| committer | Will Deacon | 2018-07-27 12:12:37 +0200 |
| commit | b63b3439b85609338e4faabd5d2588dbda137e5c (patch) | |
| tree | d11cbaeb0c03b49fd93640667747f5be5587e418 /drivers/lightnvm/pblk-core.c | |
| parent | iommu/arm-smmu-v3: Prevent any devices access to memory without registration (diff) | |
| download | kernel-qcow2-linux-b63b3439b85609338e4faabd5d2588dbda137e5c.tar.gz kernel-qcow2-linux-b63b3439b85609338e4faabd5d2588dbda137e5c.tar.xz kernel-qcow2-linux-b63b3439b85609338e4faabd5d2588dbda137e5c.zip | |
iommu/arm-smmu-v3: Abort all transactions if SMMU is enabled in kdump kernel
If we find that the SMMU is enabled during probe, we reset it by
re-initialising its registers and either enabling translation or placing
it into bypass based on the disable_bypass commandline option.
In the case of a kdump kernel, the SMMU won't have been shutdown cleanly
by the previous kernel and there may be concurrent DMA through the SMMU.
Rather than reset the SMMU to bypass, which would likely lead to rampant
data corruption, we can instead configure the SMMU to abort all incoming
transactions when we find that it is enabled from within a kdump kernel.
Reported-by: Sameer Goel <sgoel@codeaurora.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'drivers/lightnvm/pblk-core.c')
0 files changed, 0 insertions, 0 deletions