From: Yi Liu <yi.l.liu@intel.com>
To: jgg@nvidia.com, kevin.tian@intel.com
Cc: yi.l.liu@intel.com, kvm@vger.kernel.org, iommu@lists.linux.dev
Subject: [PATCH v2] iommufd: Add three missing structures in ucmd_buffer
Date: Fri, 20 Jan 2023 04:20:40 -0800 [thread overview]
Message-ID: <20230120122040.280219-1-yi.l.liu@intel.com> (raw)
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/
drivers/iommu/iommufd/main.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/iommu/iommufd/main.c b/drivers/iommu/iommufd/main.c
index 083e6fcbe10a..3fbe636c3d8a 100644
--- a/drivers/iommu/iommufd/main.c
+++ b/drivers/iommu/iommufd/main.c
@@ -252,9 +252,12 @@ union ucmd_buffer {
struct iommu_destroy destroy;
struct iommu_ioas_alloc alloc;
struct iommu_ioas_allow_iovas allow_iovas;
+ struct iommu_ioas_copy ioas_copy;
struct iommu_ioas_iova_ranges iova_ranges;
struct iommu_ioas_map map;
struct iommu_ioas_unmap unmap;
+ struct iommu_option option;
+ struct iommu_vfio_ioas vfio_ioas;
#ifdef CONFIG_IOMMUFD_TEST
struct iommu_test_cmd test;
#endif
--
2.34.1
next reply other threads:[~2023-01-20 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 12:20 Yi Liu [this message]
2023-01-23 18:30 ` [PATCH v2] iommufd: Add three missing structures in ucmd_buffer 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=20230120122040.280219-1-yi.l.liu@intel.com \
--to=yi.l.liu@intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.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 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.