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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 21 Oct 2014 14:17:48 +0200 From: Antonios Motakis <a.motakis@...tualopensystems.com> To: Alex Williamson <alex.williamson@...hat.com> Cc: kvm-arm <kvmarm@...ts.cs.columbia.edu>, Linux IOMMU <iommu@...ts.linux-foundation.org>, Will Deacon <will.deacon@....com>, VirtualOpenSystems Technical Team <tech@...tualopensystems.com>, Christoffer Dall <christoffer.dall@...aro.org>, Eric Auger <eric.auger@...aro.org>, Kim Phillips <kim.phillips@...escale.com>, Marc Zyngier <marc.zyngier@....com>, "open list:VFIO DRIVER" <kvm@...r.kernel.org>, "open list:ABI/API" <linux-api@...r.kernel.org>, open list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 2/5] vfio: introduce the VFIO_DMA_MAP_FLAG_NOEXEC flag On Mon, Oct 20, 2014 at 11:29 PM, Alex Williamson <alex.williamson@...hat.com> wrote: > On Mon, 2014-10-13 at 15:09 +0200, Antonios Motakis wrote: >> We introduce the VFIO_DMA_MAP_FLAG_NOEXEC flag to the VFIO dma map call, >> and expose its availability via the capability VFIO_DMA_NOEXEC_IOMMU. >> This way the user can control whether the XN flag will be set on the >> requested mappings. The IOMMU_NOEXEC flag needs to be available for all >> the IOMMUs of the container used. >> >> Signed-off-by: Antonios Motakis <a.motakis@...tualopensystems.com> >> --- >> include/uapi/linux/vfio.h | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h >> index 6612974..111b5e8 100644 >> --- a/include/uapi/linux/vfio.h >> +++ b/include/uapi/linux/vfio.h >> @@ -29,6 +29,7 @@ >> * capability is subject to change as groups are added or removed. >> */ >> #define VFIO_DMA_CC_IOMMU 4 >> +#define VFIO_DMA_NOEXEC_IOMMU 5 >> >> /* Check if EEH is supported */ >> #define VFIO_EEH 5 > ^^ > 5 is still already used. Feel free to convert to enum so we stop making > this mistake. Oops :) will do. > >> @@ -401,6 +402,7 @@ struct vfio_iommu_type1_dma_map { >> __u32 flags; >> #define VFIO_DMA_MAP_FLAG_READ (1 << 0) /* readable from device */ >> #define VFIO_DMA_MAP_FLAG_WRITE (1 << 1) /* writable from device */ >> +#define VFIO_DMA_MAP_FLAG_NOEXEC (1 << 2) /* not executable from device */ >> __u64 vaddr; /* Process virtual address */ >> __u64 iova; /* IO virtual address */ >> __u64 size; /* Size of mapping (bytes) */ > > > -- Antonios Motakis Virtual Open Systems -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists