From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: kevin.tian@intel.com, kvm@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH v2] iommufd: Add three missing structures in ucmd_buffer
Date: Mon, 23 Jan 2023 14:30:34 -0400 [thread overview]
Message-ID: <Y87SShqUIA5mYBVB@nvidia.com> (raw)
In-Reply-To: <20230120122040.280219-1-yi.l.liu@intel.com>
On Fri, Jan 20, 2023 at 04:20:40AM -0800, Yi Liu wrote:
> struct iommu_ioas_copy, struct iommu_option and struct iommu_vfio_ioas
> are missed in ucmd_buffer. Although they are smaller than the size of
> ucmd_buffer, it is safer to list them in ucmd_buffer explicitly.
>
> Fixes: aad37e71d5c4 ("iommufd: IOCTLs for the io_pagetable")
> Fixes: d624d6652a65 ("iommufd: vfio container FD ioctl compatibility")
> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
> ---
> v2:
> - add iommu_ioas_copy as KevinT pointed
>
> v1: https://lore.kernel.org/kvm/20230120055757.67879-1-yi.l.liu@intel.com/
Applied thanks
Jason
prev parent reply other threads:[~2023-01-23 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 12:20 [PATCH v2] iommufd: Add three missing structures in ucmd_buffer Yi Liu
2023-01-23 18:30 ` Jason Gunthorpe [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=Y87SShqUIA5mYBVB@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--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