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.dev
Subject: [git pull] IOMMU Fixes for Linux v6.1-rc7
Date: Fri, 2 Dec 2022 15:04:33 +0100 [thread overview]
Message-ID: <Y4oF8e7quzjm2kzD@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Hi Linus,
The following changes since commit b7b275e60bcd5f89771e865a8239325f86d9927d:
Linux 6.1-rc7 (2022-11-27 13:31:48 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v6.1-rc7
for you to fetch changes up to 4bedbbd782ebbe7287231fea862c158d4f08a9e3:
iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() (2022-12-02 11:45:33 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v6.1-rc7
Including:
- Intel VT-d fixes:
- IO/TLB flush fix
- Various pci_dev refcount fixes
----------------------------------------------------------------
Jacob Pan (1):
iommu/vt-d: Add a fix for devices need extra dtlb flush
Xiongfeng Wang (2):
iommu/vt-d: Fix PCI device refcount leak in has_external_pci()
iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init()
Yang Yingliang (1):
iommu/vt-d: Fix PCI device refcount leak in prq_event_thread()
drivers/iommu/intel/dmar.c | 1 +
drivers/iommu/intel/iommu.c | 73 +++++++++++++++++++++++++++++++++++++++++++--
drivers/iommu/intel/iommu.h | 4 +++
drivers/iommu/intel/svm.c | 19 ++++++++----
4 files changed, 88 insertions(+), 9 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-12-02 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:04 Joerg Roedel [this message]
2022-12-03 0:10 ` [git pull] IOMMU Fixes for Linux v6.1-rc7 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=Y4oF8e7quzjm2kzD@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--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