[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v7 10/10] xen/common: do not implicitly permit access to mapped I/O memory

>>> On 26.05.14 at 16:26, <julien.grall@xxxxxxxxxx> wrote:
> I'm still not convince, it's perfectly valid to:
>       1) call iomem_permission to set the permission
>       2) call memory_mapping
>          3) call iomem_permission to remove the permission
> In this case the memory mapping will be there without any granting. 
> Hence, we won't be able to remove those mappings.

This would be a tool stack bug imo. And yes, this is possible, but no,
I don't think one should rely on this being possible (i.e. if we
introduced ways to find such mappings and refused the permission
removal, nothing should break).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.