From: Uri Lublin <uril@redhat.com>
To: intel-gvt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Snir Sheriber <ssheribe@redhat.com>
Subject: [PATCH 1/3] i915/gvt/dmabuf: vgpu_get_plane_info: validate_range with size in bytes
Date: Sun, 14 Apr 2019 17:44:11 +0300 [thread overview]
Message-ID: <20190414144413.9708-2-uril@redhat.com> (raw)
In-Reply-To: <20190414144413.9708-1-uril@redhat.com>
size is kept in pages, validate_range gets bytes.
Signed-off-by: Uri Lublin <uril@redhat.com>
Signed-off-by: Snir Sheriber <ssheribe@redhat.com>
---
drivers/gpu/drm/i915/gvt/dmabuf.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gvt/dmabuf.c b/drivers/gpu/drm/i915/gvt/dmabuf.c
index 69a9a1b2ea4a..857e3a02d951 100644
--- a/drivers/gpu/drm/i915/gvt/dmabuf.c
+++ b/drivers/gpu/drm/i915/gvt/dmabuf.c
@@ -284,7 +284,8 @@ static int vgpu_get_plane_info(struct drm_device *dev,
return -EFAULT;
}
- if (!intel_gvt_ggtt_validate_range(vgpu, info->start, info->size)) {
+ if (!intel_gvt_ggtt_validate_range(vgpu, info->start,
+ info->size << PAGE_SHIFT)) {
gvt_vgpu_err("invalid gma addr\n");
return -EFAULT;
}
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-14 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 14:44 [PATCH 0/3] i915/gvt/dmabuf: some plane 'size' fixes Uri Lublin
2019-04-14 14:44 ` Uri Lublin [this message]
2019-04-14 14:44 ` [PATCH 2/3] i915/gvt/dmabuf: fix comment about 'size' field Uri Lublin
2019-04-14 14:44 ` [PATCH 3/3] i915/gvt/dmabuf: update_fb_info: convert size correctly Uri Lublin
2019-04-14 15:13 ` ✓ Fi.CI.BAT: success for i915/gvt/dmabuf: some plane 'size' fixes Patchwork
2019-04-14 16:38 ` ✓ Fi.CI.IGT: " Patchwork
2019-04-15 2:14 ` [PATCH 0/3] " Zhenyu Wang
2019-04-15 9:55 ` Uri Lublin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190414144413.9708-2-uril@redhat.com \
--to=uril@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=ssheribe@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox