lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <ZBhbmqprnux4q00i@nvidia.com> Date: Mon, 20 Mar 2023 10:11:54 -0300 From: Jason Gunthorpe <jgg@...dia.com> To: Nicolin Chen <nicolinc@...dia.com> Cc: Robin Murphy <robin.murphy@....com>, will@...nel.org, eric.auger@...hat.com, kevin.tian@...el.com, baolu.lu@...ux.intel.com, joro@...tes.org, shameerali.kolothum.thodi@...wei.com, jean-philippe@...aro.org, linux-arm-kernel@...ts.infradead.org, iommu@...ts.linux.dev, linux-kernel@...r.kernel.org Subject: Re: [PATCH v1 14/14] iommu/arm-smmu-v3: Add arm_smmu_cache_invalidate_user On Sun, Mar 19, 2023 at 06:32:03PM -0700, Nicolin Chen wrote: > +struct iommu_hwpt_invalidate_arm_smmuv3 { > + struct iommu_iova_range range; what is this? > + __u64 cmd[2]; > +}; You still have to do something with the SID. We can't just allow any un-validated SID value - the driver has to check the incoming SID against allowed SIDs for this iommufd_ctx Jason
Powered by blists - more mailing lists