From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v5.14-rc6
Date: Fri, 20 Aug 2021 09:54:10 +0200 [thread overview]
Message-ID: <YR9fopoKjkg2o2V1@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
Hi Linus,
The following changes since commit ff1176468d368232b684f75e82563369208bc371:
Linux 5.14-rc3 (2021-07-25 15:35:14 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.14-rc6
for you to fetch changes up to 8798d36411196da86e70b994725349c16c1119f6:
iommu/vt-d: Fix incomplete cache flush in intel_pasid_tear_down_entry() (2021-08-18 13:15:58 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.14-rc6
Including:
- Fix for a potential NULL-ptr dereference in IOMMU core code
- Two resource leak fixes
- Cache flush fix in the Intel VT-d driver
----------------------------------------------------------------
Ezequiel Garcia (1):
iommu/dma: Fix leak in non-contiguous API
Fenghua Yu (1):
iommu/vt-d: Fix PASID reference leak
Frank Wunderlich (1):
iommu: Check if group is NULL before remove device
Liu Yi L (1):
iommu/vt-d: Fix incomplete cache flush in intel_pasid_tear_down_entry()
drivers/iommu/dma-iommu.c | 1 +
drivers/iommu/intel/pasid.c | 10 ++++++++--
drivers/iommu/intel/pasid.h | 6 ++++++
drivers/iommu/intel/svm.c | 3 ++-
drivers/iommu/iommu.c | 3 +++
5 files changed, 20 insertions(+), 3 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-08-20 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 7:54 Joerg Roedel [this message]
2021-08-20 20:09 ` [git pull] IOMMU Fixes for Linux v5.14-rc6 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=YR9fopoKjkg2o2V1@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).