All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org,
	Guoqing Jiang <guoqing.jiang@linux.dev>
Subject: [PATCH 0/2] iommu/vt-d: Fixes for v5.17-rc2
Date: Fri, 28 Jan 2022 11:10:00 +0800	[thread overview]
Message-ID: <20220128031002.2219155-1-baolu.lu@linux.intel.com> (raw)

Hi Joerg,

Two fixes are queued for v5.17. They aim to fix:

 - Fix PCI bus rescan device hot add;
 - Fix potential memory leak in intel_setup_irq_remapping().

Please consider them for the iommu/fix branch.

Best regards,
Lu Baolu

Guoqing Jiang (1):
  iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()

Jacob Pan (1):
  iommu/vt-d: Fix PCI bus rescan device hot add

 include/linux/iommu.h               |  1 +
 drivers/iommu/intel/dmar.c          | 71 +++++++++++++++++++++--------
 drivers/iommu/intel/irq_remapping.c | 13 ++++--
 drivers/iommu/iommu.c               |  1 +
 4 files changed, 64 insertions(+), 22 deletions(-)

-- 
2.25.1

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

             reply	other threads:[~2022-01-28  3:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  3:10 Lu Baolu [this message]
2022-01-28  3:10 ` [PATCH 1/2] iommu/vt-d: Fix PCI bus rescan device hot add Lu Baolu
2022-01-30  7:43   ` Joerg Roedel
2022-01-31 13:53     ` Robin Murphy
2022-01-31 15:52       ` Joerg Roedel
2022-02-01 19:19         ` Jacob Pan
2022-02-03  8:25           ` Joerg Roedel
2022-02-09 21:52             ` Jacob Pan
2022-02-14 10:31               ` Joerg Roedel
2022-02-01 18:55     ` Jacob Pan
2022-01-28  3:10 ` [PATCH 2/2] iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() Lu Baolu
2022-01-31 15:53   ` 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=20220128031002.2219155-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=guoqing.jiang@linux.dev \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.