From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v5.4-rc1
Date: Sat, 28 Sep 2019 21:10:17 +0200 [thread overview]
Message-ID: <20190928191007.GA7565@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]
Hi Linus,
The following changes since commit e95adb9add75affb98570a518c902f50e5fcce1b:
Merge branches 'arm/omap', 'arm/exynos', 'arm/smmu', 'arm/mediatek', 'arm/qcom', 'arm/renesas', 'x86/amd', 'x86/vt-d' and 'core' into next (2019-09-11 12:39:19 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-5.4-rc1
for you to fetch changes up to 2a78f9962565e53b78363eaf516eb052009e8020:
iommu/amd: Lock code paths traversing protection_domain->dev_list (2019-09-28 14:44:13 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.4-rc1
A couple of fixes for the AMD IOMMU driver have piled up:
* Some fixes for the reworked IO page-table which caused memory
leaks or did not allow to downgrade mappings under some
conditions.
* Locking fixes to fix a couple of possible races around
accessing 'struct protection_domain'. The races got introduced
when the dma-ops path became lock-less in the fast-path.
----------------------------------------------------------------
Andrei Dulea (4):
iommu/amd: Fix pages leak in free_pagetable()
iommu/amd: Fix downgrading default page-sizes in alloc_pte()
iommu/amd: Introduce first_pte_l7() helper
iommu/amd: Unmap all L7 PTEs when downgrading page-sizes
Filippo Sironi (1):
iommu/amd: Wait for completion of IOTLB flush in attach_device
Joerg Roedel (6):
iommu/amd: Remove domain->updated
iommu/amd: Remove amd_iommu_devtable_lock
iommu/amd: Take domain->lock for complete attach/detach path
iommu/amd: Check for busy devices earlier in attach_device()
iommu/amd: Lock dev_data in attach/detach code paths
iommu/amd: Lock code paths traversing protection_domain->dev_list
drivers/iommu/amd_iommu.c | 229 ++++++++++++++++++++++++----------------
drivers/iommu/amd_iommu_types.h | 4 +-
2 files changed, 139 insertions(+), 94 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-09-28 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 19:10 Joerg Roedel [this message]
2019-09-29 17:50 ` [git pull] IOMMU Fixes for Linux v5.4-rc1 pr-tracker-bot
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=20190928191007.GA7565@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).