From: Robin Murphy <robin.murphy@arm.com>
To: Marc Zyngier <maz@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Eric Auger <eric.auger@redhat.com>,
Joerg Roedel <jroedel@suse.de>, Will Deacon <will@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] iommu/dma: Fix MSI reservation allocation
Date: Wed, 4 Mar 2020 12:36:54 +0000 [thread overview]
Message-ID: <35a91284-619e-398a-decc-2e3879702335@arm.com> (raw)
In-Reply-To: <20200304111117.3540-1-maz@kernel.org>
On 04/03/2020 11:11 am, Marc Zyngier wrote:
> The way cookie_init_hw_msi_region() allocates the iommu_dma_msi_page
> structures doesn't match the way iommu_put_dma_cookie() frees them.
>
> The former performs a single allocation of all the required structures,
> while the latter tries to free them one at a time. It doesn't quite
> work for the main use case (the GICv3 ITS where the range is 64kB)
> when the base granule size is 4kB.
>
> This leads to a nice slab corruption on teardown, which is easily
> observable by simply creating a VF on a SRIOV-capable device, and
> tearing it down immediately (no need to even make use of it).
> Fortunately, this only affects systems where the ITS isn't translated
> by the SMMU, which are both rare and non-standard.
>
> Fix it by allocating iommu_dma_msi_page structures one at a time.
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Fixes: 7c1b058c8b5a3 ("iommu/dma: Handle IOMMU API reserved regions")
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Joerg Roedel <jroedel@suse.de>
> Cc: Will Deacon <will@kernel.org>
> Cc: stable@vger.kernel.org
> ---
> * From v1:
> - Got rid of the superfluous error handling (Robin)
> - Clarified that it only affects a very small set of systems
> - Added Eric's RB (which I assume still stands)
>
> drivers/iommu/dma-iommu.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
> index a2e96a5fd9a7..ba128d1cdaee 100644
> --- a/drivers/iommu/dma-iommu.c
> +++ b/drivers/iommu/dma-iommu.c
> @@ -177,15 +177,15 @@ static int cookie_init_hw_msi_region(struct iommu_dma_cookie *cookie,
> start -= iova_offset(iovad, start);
> num_pages = iova_align(iovad, end - start) >> iova_shift(iovad);
>
> - msi_page = kcalloc(num_pages, sizeof(*msi_page), GFP_KERNEL);
> - if (!msi_page)
> - return -ENOMEM;
> -
> for (i = 0; i < num_pages; i++) {
> - msi_page[i].phys = start;
> - msi_page[i].iova = start;
> - INIT_LIST_HEAD(&msi_page[i].list);
> - list_add(&msi_page[i].list, &cookie->msi_page_list);
> + msi_page = kmalloc(sizeof(*msi_page), GFP_KERNEL);
> + if (!msi_page)
> + return -ENOMEM;
> +
> + msi_page->phys = start;
> + msi_page->iova = start;
> + INIT_LIST_HEAD(&msi_page->list);
> + list_add(&msi_page->list, &cookie->msi_page_list);
> start += iovad->granule;
> }
>
>
next prev parent reply other threads:[~2020-03-04 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 11:11 Marc Zyngier
2020-03-04 12:36 ` Robin Murphy [this message]
2020-03-04 15:28 ` 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=35a91284-619e-398a-decc-2e3879702335@arm.com \
--to=robin.murphy@arm.com \
--cc=eric.auger@redhat.com \
--cc=jroedel@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=stable@vger.kernel.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®