The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: will@kernel.org, robin.murphy@arm.com, jgg@ziepe.ca,
	 kevin.tian@intel.com, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org,  oliver.yang@linux.alibaba.com,
	zhuo.song@linux.alibaba.com
Subject: Re: [PATCH 0/4] iommu: Fix SVA, iommufd, and iommupt error paths
Date: Mon, 10 Aug 2026 09:52:11 +0200	[thread overview]
Message-ID: <anmDHI07-PDaynZD@8bytes.org> (raw)
In-Reply-To: <cover.1785050951.git.xueshuai@linux.alibaba.com>

On Sun, Jul 26, 2026 at 03:43:28PM +0800, Shuai Xue wrote:
> Shuai Xue (4):
>   iommu/sva: Set handle->dev before the SVA handle is visible
>   iommufd: Avoid locking internal accesses during unmap
>   iommufd: Release current IOAS on xa_store() failure
>   iommupt: Return zero for invalid iova_to_phys() ranges

Applied, thanks.

      parent reply	other threads:[~2026-08-10  7:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26  7:43 [PATCH 0/4] iommu: Fix SVA, iommufd, and iommupt error paths Shuai Xue
2026-07-26  7:43 ` [PATCH 1/4] iommu/sva: Set handle->dev before the SVA handle is visible Shuai Xue
2026-07-27  9:38   ` Tian, Kevin
2026-07-27 10:14     ` Shuai Xue
2026-07-29  2:59   ` Baolu Lu
2026-07-26  7:43 ` [PATCH 2/4] iommufd: Avoid locking internal accesses during unmap Shuai Xue
2026-07-27  9:38   ` Tian, Kevin
2026-07-26  7:43 ` [PATCH 3/4] iommufd: Release current IOAS on xa_store() failure Shuai Xue
2026-07-27  9:39   ` Tian, Kevin
2026-07-26  7:43 ` [PATCH 4/4] iommupt: Return zero for invalid iova_to_phys() ranges Shuai Xue
2026-07-27  9:39   ` Tian, Kevin
2026-07-29  2:59   ` Baolu Lu
2026-08-07 22:45 ` [PATCH 0/4] iommu: Fix SVA, iommufd, and iommupt error paths Jason Gunthorpe
2026-08-10  7:52 ` Jörg Rödel [this message]

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=anmDHI07-PDaynZD@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.yang@linux.alibaba.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=xueshuai@linux.alibaba.com \
    --cc=zhuo.song@linux.alibaba.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