Linux IOMMU Development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Pranjal Shrivastava <praan@google.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: David Woodhouse <dwmw2@infradead.org>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Samiullah Khawaja <skhawaja@google.com>
Subject: Re: [PATCH 0/2] iommu/vt-d: Fix issues on probe error path
Date: Mon, 1 Jun 2026 15:11:39 +0800	[thread overview]
Message-ID: <b1991d9c-ae0e-49a3-bc28-623fa554d428@linux.intel.com> (raw)
In-Reply-To: <20260531170254.60493-1-praan@google.com>

On 6/1/26 01:02, Pranjal Shrivastava wrote:
> This series addresses two pre-existing issues in the Intel VT-d driver's
> probe error path. These issues were identified by Sashiko during the
> review of the ATS series [1].
> 
> The first patch fixes an RB-tree corruption that occurs when probing
> non-ATS devices. The second patch fixes a UAF by ensuring the per-device
> private data pointer is cleared before freeing memory on failure.
> 
> [1]https://sashiko.dev/#/patchset/20260525184347.4059549-1- 
> praan@google.com?part=4
> 
> v2
> - Updated the Fixes tag for Patch 2 based on feedback from Lu.
> 
> Thanks,
> Praan
> 
> Pranjal Shrivastava (2):
>    iommu/vt-d: Fix RB-tree corruption in probe error path
>    iommu/vt-d: Fix Use-After-Free in probe error path
> 
>   drivers/iommu/intel/iommu.c | 7 ++++++-
>   1 file changed, 6 insertions(+), 1 deletion(-)

Queued these two fix patches for linux-next.

I noticed that Sashiko reported two pre-existing issues here:

https://sashiko.dev/#/patchset/20260531170254.60493-1-praan%40google.com

I will follow up with fixes for them in separate patches.

Thanks,
baolu

  parent reply	other threads:[~2026-06-01  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-31 17:02 [PATCH 0/2] iommu/vt-d: Fix issues on probe error path Pranjal Shrivastava
2026-05-31 17:02 ` [PATCH v2 1/2] iommu/vt-d: Fix RB-tree corruption in " Pranjal Shrivastava
2026-05-31 17:02 ` [PATCH v2 2/2] iommu/vt-d: Fix Use-After-Free " Pranjal Shrivastava
2026-06-01  7:11 ` Baolu Lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-29 11:34 [PATCH 0/2] iommu/vt-d: Fix issues on " Pranjal Shrivastava

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=b1991d9c-ae0e-49a3-bc28-623fa554d428@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=praan@google.com \
    --cc=robin.murphy@arm.com \
    --cc=skhawaja@google.com \
    --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