kernel.git/drivers/gpu/drm/vmwgfx, branch linux-3.15.y

drm/vmwgfx: Fix incorrect write to read-only register v2:

2014-07-09T18:21:27Z

commit 4e578080ed3262ed2c3985868539bc66218d25c0 upstream. Commit "drm/vmwgfx: correct fb_fix_screeninfo.line_length", while fixing a vmwgfx fbdev bug, also writes the pitch to a supposedly read-only register: SVGA_REG_BYTES_PER_LINE, while it should be (and also in fact is) written to SVGA_REG_PITCHLOCK. This patch is Cc'd stable because of the unknown effects writing to this register might have, particularly on older device versions. v2: Updated log message. Cc: Christopher Friedt Tested-by: Christopher Friedt Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz Signed-off-by: Greg Kroah-Hartman

drm/vmwgfx: Make sure user-space can't DMA across buffer object boundaries v2

2014-04-24T06:45:25Z

We already check that the buffer object we're accessing is registered with the file. Now also make sure that we can't DMA across buffer object boundaries. v2: Code commenting update. Cc: stable@vger.kernel.org Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz

drm/vmwgfx: correct fb_fix_screeninfo.line_length

2014-04-03T07:34:06Z

Previously, the vmwgfx_fb driver would allow users to call FBIOSET_VINFO, but it would not adjust the FINFO properly, resulting in distorted screen rendering. The patch corrects that behaviour. See https://bugs.gentoo.org/show_bug.cgi?id=494794 for examples. Cc: stable@vger.kernel.org Signed-off-by: Christopher Friedt Reviewed-by: Thomas Hellstrom

drm/vmwgfx: Remove authorization requirements around some more ioctls

2014-04-03T07:31:38Z

These ioctls require a valid handle referenced by the caller to succeed, which implies that the caller has or has had sufficient privileges. Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul

drm/vmwgfx: Fix query buffer locking order violation

2014-04-03T07:31:37Z

The query buffers were reserved while holding the binding mutex, which caused a circular locking dependency. Cc: stable@vger.kernel.org Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul

drm: Replace crtc fb with primary plane fb (v3)

2014-04-02T00:18:28Z

Now that CRTC's have a primary plane, there's no need to track the framebuffer in the CRTC. Replace all references to the CRTC fb with the primary plane's fb. This patch was generated by the Coccinelle semantic patching tool using the following rules: @@ struct drm_crtc C; @@ - (C).fb + C.primary->fb @@ struct drm_crtc *C; @@ - (C)->fb + C->primary->fb v3: Generate patch via coccinelle. Actual removal of crtc->fb has been moved to a subsequent patch. v2: Fixup several lingering crtc->fb instances that were missed in the first patch iteration. [Rob Clark] Signed-off-by: Matt Roper Reviewed-by: Rob Clark

drm/vmwgfx: Bump driver minor and date

2014-03-28T13:19:05Z

Signal availability of prime fd reference ioctls and render nodes. Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul

drm/vmwgfx: Enable render nodes

2014-03-28T13:19:04Z

Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul

drm/vmwgfx: Tighten the security around buffer maps

2014-03-28T13:19:04Z

Make sure only buffer objects that are referenced by the client can be mapped. Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul

drm/vmwgfx: Tighten security around surface sharing v2

2014-03-28T13:19:03Z

If using legacy (non-prime) surface sharing, only allow surfaces to be shared between clients with the same master. This will block malicious clients from peeking at contents at surfaces from other (possibly vt-switched) masters. v2: s/legacy_client/primary_client/ Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul