[Xen-devel] [RFC PATCH 38/60] hyper_dmabuf: preventing self exporting of dma_buf

[Dongwon Kim <dongwon.kim@xxxxxxxxx>]

Adding ID check to make sure a dma-buf is exported externally
since hyper_dmabuf only allows to export a dmabuf to a different
VM.

Signed-off-by: Dongwon Kim <dongwon.kim@xxxxxxxxx>
---
 drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c 
b/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c
index 12f7ce4..b77b156 100644
--- a/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c
+++ b/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c
@@ -103,6 +103,12 @@ static int hyper_dmabuf_export_remote_ioctl(struct file 
*filp, void *data)
 
        export_remote_attr = (struct ioctl_hyper_dmabuf_export_remote *)data;
 
+       if (hyper_dmabuf_private.domid == export_remote_attr->remote_domain) {
+               dev_err(hyper_dmabuf_private.device,
+                       "exporting to the same VM is not permitted\n");
+               return -EINVAL;
+       }
+
        dma_buf = dma_buf_get(export_remote_attr->dmabuf_fd);
 
        if (IS_ERR(dma_buf)) {
-- 
2.7.4


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel