From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Xiongfeng Wang <wangxiongfeng2@huawei.com>,
Yang Yingliang <yangyingliang@huawei.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] [PULL REQUEST] iommu/vt-d: Fixes for v6.1-rc8
Date: Thu, 1 Dec 2022 12:01:23 +0800 [thread overview]
Message-ID: <20221201040127.1962750-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
Below fixes are queued for v6.1. They aim to:
- Add a fix to handle a QAT device quirk.
- Fix 3 PCI device refcount leaks.
This series is also available at github.
https://github.com/LuBaolu/intel-iommu/commits/vtd-fix-for-v6.1-rc8
Please consider it for the iommu/fix branch.
Best regards,
Lu Baolu
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/iommu.h | 4 ++
drivers/iommu/intel/dmar.c | 1 +
drivers/iommu/intel/iommu.c | 73 +++++++++++++++++++++++++++++++++++--
drivers/iommu/intel/svm.c | 19 +++++++---
4 files changed, 88 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-01 4:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 4:01 Lu Baolu [this message]
2022-12-01 4:01 ` [PATCH 1/4] iommu/vt-d: Add a fix for devices need extra dtlb flush Lu Baolu
2022-12-01 8:36 ` Baolu Lu
2022-12-01 4:01 ` [PATCH 2/4] iommu/vt-d: Fix PCI device refcount leak in prq_event_thread() Lu Baolu
2022-12-01 4:01 ` [PATCH 3/4] iommu/vt-d: Fix PCI device refcount leak in has_external_pci() Lu Baolu
2022-12-01 4:01 ` [PATCH 4/4] iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() Lu Baolu
2022-12-02 10:47 ` [PATCH 0/4] [PULL REQUEST] iommu/vt-d: Fixes for v6.1-rc8 Joerg Roedel
2022-12-03 0:54 ` Jacob Pan
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=20221201040127.1962750-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangxiongfeng2@huawei.com \
--cc=yangyingliang@huawei.com \
/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