From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Timur Tabi <timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Sameer Goel <sgoel-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Subject: Re: [PATCH] iommu/arm-smmu-v3: Set GBPA to abort all transactions
Date: Thu, 5 Apr 2018 12:26:23 +0100 [thread overview]
Message-ID: <20180405112622.GE23485@arm.com> (raw)
In-Reply-To: <1522247980-31892-1-git-send-email-timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
On Wed, Mar 28, 2018 at 09:39:40AM -0500, Timur Tabi wrote:
> From: Sameer Goel <sgoel-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
>
> Set SMMU_GBPA to abort all incoming translations during the SMMU reset
> when SMMUEN==0.
>
> This prevents a race condition where a stray DMA from the crashed primary
> kernel can try to access an IOVA address as an invalid PA when SMMU is
> disabled during reset in the crash kernel.
>
> Signed-off-by: Sameer Goel <sgoel-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
> ---
> drivers/iommu/arm-smmu-v3.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/iommu/arm-smmu-v3.c b/drivers/iommu/arm-smmu-v3.c
> index 3f2f1fc68b52..c04a89310c59 100644
> --- a/drivers/iommu/arm-smmu-v3.c
> +++ b/drivers/iommu/arm-smmu-v3.c
> @@ -2458,6 +2458,18 @@ static int arm_smmu_device_reset(struct arm_smmu_device *smmu, bool bypass)
> if (reg & CR0_SMMUEN)
> dev_warn(smmu->dev, "SMMU currently enabled! Resetting...\n");
>
> + /*
> + * Abort all incoming translations. This can happen in a kdump case
> + * where SMMU is initialized when a prior DMA is pending. Just
> + * disabling the SMMU in this case might result in writes to invalid
> + * PAs.
> + */
> + ret = arm_smmu_update_gbpa(smmu, 1, GBPA_ABORT);
> + if (ret) {
> + dev_err(smmu->dev, "GBPA not responding to update\n");
> + return ret;
> + }
This needs to be predicated on the disable_bypass option, otherwise I think
it will cause regressions for systems that rely on passthrough.
Will
next prev parent reply other threads:[~2018-04-05 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:39 [PATCH] iommu/arm-smmu-v3: Set GBPA to abort all transactions Timur Tabi
2018-03-28 15:00 ` Marc Zyngier
2018-04-11 15:58 ` Goel, Sameer
[not found] ` <3772fb2d-01b7-4820-6d13-a0263654dabc-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-11 16:54 ` Marc Zyngier
[not found] ` <438a6180-fca8-d3a1-985f-e595529911f3-5wv7dgnIgG8@public.gmane.org>
2018-04-12 10:17 ` Robin Murphy
[not found] ` <7756f245-6c63-92d4-d101-4040a45b660b-5wv7dgnIgG8@public.gmane.org>
2018-04-12 10:55 ` Will Deacon
2018-04-12 11:56 ` Marc Zyngier
[not found] ` <265a41d4-ec3c-6697-0340-6830807ea10f-5wv7dgnIgG8@public.gmane.org>
2018-05-11 16:15 ` Goel, Sameer
2018-05-11 20:52 ` Nate Watterson
[not found] ` <1522247980-31892-1-git-send-email-timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-05 11:26 ` Will Deacon [this message]
2018-04-11 15:54 ` Goel, Sameer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180405112622.GE23485@arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=sgoel-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).