On Tue, May 12, 2015 at 01:38:59AM +1000, Alexey Kardashevskiy wrote: >At the moment DMA map/unmap requests are handled irrespective to >the container's state. This allows the user space to pin memory which >it might not be allowed to pin. > >This adds checks to MAP/UNMAP that the container is enabled, otherwise >-EPERM is returned. > >Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> >[aw: for the vfio related changes] >Acked-by: Alex Williamson <alex.william...@redhat.com> >Reviewed-by: David Gibson <da...@gibson.dropbear.id.au>
Reviewed-by: Gavin Shan <gws...@linux.vnet.ibm.com> Thanks, Gavin >--- > drivers/vfio/vfio_iommu_spapr_tce.c | 6 ++++++ > 1 file changed, 6 insertions(+) > >diff --git a/drivers/vfio/vfio_iommu_spapr_tce.c >b/drivers/vfio/vfio_iommu_spapr_tce.c >index 40583f9..e21479c 100644 >--- a/drivers/vfio/vfio_iommu_spapr_tce.c >+++ b/drivers/vfio/vfio_iommu_spapr_tce.c >@@ -318,6 +318,9 @@ static long tce_iommu_ioctl(void *iommu_data, > struct iommu_table *tbl = container->tbl; > unsigned long tce; > >+ if (!container->enabled) >+ return -EPERM; >+ > if (!tbl) > return -ENXIO; > >@@ -362,6 +365,9 @@ static long tce_iommu_ioctl(void *iommu_data, > struct vfio_iommu_type1_dma_unmap param; > struct iommu_table *tbl = container->tbl; > >+ if (!container->enabled) >+ return -EPERM; >+ > if (WARN_ON(!tbl)) > return -ENXIO; > >-- >2.4.0.rc3.8.gfb3e7d5 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
