Re: [PATCH v5 4/5] iommu/uapi: Handle data and argsz filled by users

2020-07-21 Thread Jacob Pan
On Fri, 17 Jul 2020 13:59:54 -0600 Alex Williamson wrote: > On Thu, 16 Jul 2020 11:45:16 -0700 > Jacob Pan wrote: > > > IOMMU UAPI data has a user filled argsz field which indicates the > > data length comes with the API call. User data is not trusted, > > argsz must be validated based on the

Re: [PATCH v5 4/5] iommu/uapi: Handle data and argsz filled by users

2020-07-21 Thread Jacob Pan
On Fri, 17 Jul 2020 17:58:04 +0200 Auger Eric wrote: > Hi Jacob, > On 7/16/20 8:45 PM, Jacob Pan wrote: > > Could you share a branch? I was not able to apply this on either > iommu/next or master? > Will push it to github for the next version. This set is based on v5.8-rc1 and my fixes for

Re: [PATCH v5 4/5] iommu/uapi: Handle data and argsz filled by users

2020-07-17 Thread Alex Williamson
On Thu, 16 Jul 2020 11:45:16 -0700 Jacob Pan wrote: > IOMMU UAPI data has a user filled argsz field which indicates the data > length comes with the API call. User data is not trusted, argsz must be > validated based on the current kernel data size, mandatory data size, > and feature flags. > >

Re: [PATCH v5 4/5] iommu/uapi: Handle data and argsz filled by users

2020-07-17 Thread Auger Eric
Hi Jacob, On 7/16/20 8:45 PM, Jacob Pan wrote: Could you share a branch? I was not able to apply this on either iommu/next or master? > IOMMU UAPI data has a user filled argsz field which indicates the data > length comes with the API call. s/ comes with the API call/ of the structure User data

[PATCH v5 4/5] iommu/uapi: Handle data and argsz filled by users

2020-07-16 Thread Jacob Pan
IOMMU UAPI data has a user filled argsz field which indicates the data length comes with the API call. User data is not trusted, argsz must be validated based on the current kernel data size, mandatory data size, and feature flags. User data may also be extended, results in possible argsz