[RFC PATCH 55/60] hyper_dmabuf: fixed wrong send_req call

Dongwon Kim dongwon.kim at intel.com
Tue Dec 19 19:30:11 UTC 2017

From: Mateusz Polrola <mateuszx.potrola at intel.com>

Wrong vmid is used in case of sending HYPER_DMABUF_EXPORT_FD_FAILED
message. Instead of vmid, hypder dmabuf id is being used.

Signed-off-by: Mateusz Polrola <mateuszx.potrola at intel.com>
Signed-off-by: Dongwon Kim <dongwon.kim at intel.com>
 drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c b/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c
index d1970c8..ca6edf2 100644
--- a/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c
+++ b/drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c
@@ -473,7 +473,7 @@ static int hyper_dmabuf_export_fd_ioctl(struct file *filp, void *data)
 		hyper_dmabuf_create_req(req, HYPER_DMABUF_EXPORT_FD_FAILED,
-		bknd_ops->send_req(op[0], req, false);
+		bknd_ops->send_req(HYPER_DMABUF_DOM_ID(imported->hid), req, false);
 			"Failed to create sgt or notify exporter\n");

More information about the dri-devel mailing list