From: Greg KH <greg@kroah.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: stable@vger.kernel.org, "Monroy,
Rodrigo Axel" <rodrigo.axel.monroy@intel.com>,
"Orrala Contreras, Alfredo" <alfredo.orrala.contreras@intel.com>,
Hang Yuan <hang.yuan@intel.com>
Subject: Re: [PATCH 4.14 backport] drm/i915/gvt: Fix mmap range check
Date: Thu, 24 Jan 2019 19:34:19 +0100 [thread overview]
Message-ID: <20190124183419.GA23507@kroah.com> (raw)
In-Reply-To: <20190122021501.25856-1-zhenyuw@linux.intel.com>
On Tue, Jan 22, 2019 at 10:15:01AM +0800, Zhenyu Wang wrote:
> This is to fix missed mmap range check on vGPU bar2 region
> and only allow to map vGPU allocated GMADDR range, which means
> user space should support sparse mmap to get proper offset for
> mmap vGPU aperture. And this takes care of actual pgoff in mmap
> request as original code always does from beginning of vGPU
> aperture.
>
> Fixes: 659643f7d814 ("drm/i915/gvt/kvmgt: add vfio/mdev support to KVMGT")
> Cc: "Monroy, Rodrigo Axel" <rodrigo.axel.monroy@intel.com>
> Cc: "Orrala Contreras, Alfredo" <alfredo.orrala.contreras@intel.com>
> Cc: stable@vger.kernel.org # v4.10+
> Reviewed-by: Hang Yuan <hang.yuan@intel.com>
> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
> ---
> Note: This is backported version of upstream
> commit 51b00d8509dc ("drm/i915/gvt: Fix mmap range check") for 4.14.x stable.
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2019-01-24 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 2:15 [PATCH 4.14 backport] drm/i915/gvt: Fix mmap range check Zhenyu Wang
2019-01-24 18:34 ` Greg KH [this message]
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=20190124183419.GA23507@kroah.com \
--to=greg@kroah.com \
--cc=alfredo.orrala.contreras@intel.com \
--cc=hang.yuan@intel.com \
--cc=rodrigo.axel.monroy@intel.com \
--cc=stable@vger.kernel.org \
--cc=zhenyuw@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.