From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <iommu@lists.linux.dev>, Kevin Tian <kevin.tian@intel.com>,
<patches@lists.linux.dev>, Yi Liu <yi.l.liu@intel.com>
Subject: Re: [PATCH] iommufd: Check the domain owner of the parent before creating a nesting domain
Date: Thu, 29 Aug 2024 09:19:43 -0700 [thread overview]
Message-ID: <ZtCfnx/NKbrjRiJB@Asurada-Nvidia> (raw)
In-Reply-To: <0-v1-c8770519edde+1a-iommufd_nesting_ops_jgg@nvidia.com>
On Thu, Aug 29, 2024 at 10:19:59AM -0300, Jason Gunthorpe wrote:
> This check was missed, before we can pass a struct iommu_domain to a
> driver callback we need to validate that the domain was created by that
> driver.
>
> Fixes: bd529dbb661d ("iommufd: Add a nested HW pagetable object")
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
next prev parent reply other threads:[~2024-08-29 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 13:19 [PATCH] iommufd: Check the domain owner of the parent before creating a nesting domain Jason Gunthorpe
2024-08-29 16:19 ` Nicolin Chen [this message]
2024-09-05 15:01 ` Jason Gunthorpe
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=ZtCfnx/NKbrjRiJB@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=patches@lists.linux.dev \
--cc=yi.l.liu@intel.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