From: Jerry Snitselaar <jsnitsel@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Filippo Sironi <sironi@amazon.de>,
iommu@lists.linux-foundation.org, jroedel@suse.de
Subject: Re: [PATCH 5/6] iommu/amd: Lock dev_data in attach/detach code paths
Date: Wed, 25 Sep 2019 23:41:38 -0700 [thread overview]
Message-ID: <20190926064138.numemgo2qc4nch2o@cantor> (raw)
In-Reply-To: <20190925132300.3038-6-joro@8bytes.org>
On Wed Sep 25 19, Joerg Roedel wrote:
>From: Joerg Roedel <jroedel@suse.de>
>
>Make sure that attaching a detaching a device can't race against each
>other and protect the iommu_dev_data with a spin_lock in these code
>paths.
>
>Fixes: 92d420ec028d ("iommu/amd: Relax locking in dma_ops path")
>Signed-off-by: Joerg Roedel <jroedel@suse.de>
>---
> drivers/iommu/amd_iommu.c | 9 +++++++++
> drivers/iommu/amd_iommu_types.h | 3 +++
> 2 files changed, 12 insertions(+)
>
>diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
>index 459247c32dc0..bac4e20a5919 100644
>--- a/drivers/iommu/amd_iommu.c
>+++ b/drivers/iommu/amd_iommu.c
>@@ -201,6 +201,7 @@ static struct iommu_dev_data *alloc_dev_data(u16 devid)
> if (!dev_data)
> return NULL;
>
>+ spin_lock_init(&dev_data->lock);
> dev_data->devid = devid;
> ratelimit_default_init(&dev_data->rs);
>
>@@ -2157,6 +2158,8 @@ static int attach_device(struct device *dev,
>
> dev_data = get_dev_data(dev);
>
>+ spin_lock(&dev_data->lock);
>+
> ret = -EBUSY;
> if (dev_data->domain != NULL)
> goto out;
>@@ -2199,6 +2202,8 @@ static int attach_device(struct device *dev,
> domain_flush_complete(domain);
>
> out:
>+ spin_unlock(&dev_data->lock);
>+
> spin_unlock_irqrestore(&domain->lock, flags);
>
> return ret;
>@@ -2218,6 +2223,8 @@ static void detach_device(struct device *dev)
>
> spin_lock_irqsave(&domain->lock, flags);
>
>+ spin_lock(&dev_data->lock);
>+
> /*
> * First check if the device is still attached. It might already
> * be detached from its domain because the generic
>@@ -2240,6 +2247,8 @@ static void detach_device(struct device *dev)
> dev_data->ats.enabled = false;
>
> out:
>+ spin_unlock(&dev_data->lock);
>+
> spin_unlock_irqrestore(&domain->lock, flags);
> }
>
>diff --git a/drivers/iommu/amd_iommu_types.h b/drivers/iommu/amd_iommu_types.h
>index 0186501ab971..c9c1612d52e0 100644
>--- a/drivers/iommu/amd_iommu_types.h
>+++ b/drivers/iommu/amd_iommu_types.h
>@@ -633,6 +633,9 @@ struct devid_map {
> * This struct contains device specific data for the IOMMU
> */
> struct iommu_dev_data {
>+ /*Protect against attach/detach races */
>+ spinlock_t lock;
>+
> struct list_head list; /* For domain->dev_list */
> struct llist_node dev_data_list; /* For global dev_data_list */
> struct protection_domain *domain; /* Domain the device is bound to */
>--
>2.17.1
>
>_______________________________________________
>iommu mailing list
>iommu@lists.linux-foundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/iommu
Reviewed-by: Jerry Snitselaar <jsnitsel@redhat.com>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-09-26 6:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 13:22 [PATCH 0/6] iommu/amd: Locking Fixes Joerg Roedel
2019-09-25 13:22 ` [PATCH 1/6] iommu/amd: Remove domain->updated Joerg Roedel
2019-09-25 15:45 ` Sironi, Filippo via iommu
2019-09-26 6:18 ` Jerry Snitselaar
2019-09-25 13:22 ` [PATCH 2/6] iommu/amd: Remove amd_iommu_devtable_lock Joerg Roedel
2019-09-25 15:50 ` Sironi, Filippo via iommu
2019-09-25 15:52 ` Sironi, Filippo via iommu
2019-09-26 6:24 ` Jerry Snitselaar
2019-09-25 13:22 ` [PATCH 3/6] iommu/amd: Take domain->lock for complete attach/detach path Joerg Roedel
2019-09-25 15:53 ` Sironi, Filippo via iommu
2019-09-26 6:34 ` Jerry Snitselaar
2019-09-25 13:22 ` [PATCH 4/6] iommu/amd: Check for busy devices earlier in attach_device() Joerg Roedel
2019-09-25 15:55 ` Sironi, Filippo via iommu
2019-09-26 6:37 ` Jerry Snitselaar
2019-09-25 13:22 ` [PATCH 5/6] iommu/amd: Lock dev_data in attach/detach code paths Joerg Roedel
2019-09-25 15:56 ` Sironi, Filippo via iommu
2019-09-26 6:41 ` Jerry Snitselaar [this message]
2019-09-25 13:23 ` [PATCH 6/6] iommu/amd: Lock code paths traversing protection_domain->dev_list Joerg Roedel
2019-09-25 15:58 ` Sironi, Filippo via iommu
2019-09-26 6:48 ` Jerry Snitselaar
2019-09-26 0:25 ` [PATCH 0/6] iommu/amd: Locking Fixes Jerry Snitselaar
2019-09-26 5:46 ` Joerg Roedel
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=20190926064138.numemgo2qc4nch2o@cantor \
--to=jsnitsel@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=sironi@amazon.de \
/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