xf86-video-vmware: Changes to 'master'

[GitLab Mirror]

 configure.ac           |   10 ++++++
 saa/saa.c              |   72 ++++++++++++++++++++++++++++++++++++++++++-------
 saa/saa_pixmap.c       |    3 +-
 saa/saa_priv.h         |   10 ++++++
 vmwgfx/vmwgfx_dri2.c   |   43 +++++++++++++++++++++--------
 vmwgfx/vmwgfx_driver.c |    5 ++-
 vmwgfx/vmwgfx_driver.h |   10 ++++++
 7 files changed, 130 insertions(+), 23 deletions(-)

New commits:
commit d31e8e77e1453c26a02f24b26d96b4660d29e1df
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Tue Nov 27 08:37:13 2018 +0100

    vmwgfx: Fix invalid memory accesses in CloseScreen
    
    Some of the CloseScreen callbacks were referencing XA objects so move the
    destruction of the XA state tracker to the end of drv_close_screen to avoid
    referencing freed resources.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Deepak Rawat <drawat at vmware.com>

commit 79d066da48dddcbdfcf41ecbe29cd96aaae2e11c
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Tue Nov 27 08:29:06 2018 +0100

    saa: Make sure damage destruction happens at the correct location
    
    Incorrect DestroyPixmap wrapping previously made the destruction of damage
    objects typically happen in damageDestroyPixmap(), leaving a dangling
    damage pointer in saa_destroy_pixmap() which was only cleared. However in
    some cases that caused us to leak damage objects.
    
    Rework saa initialization somewhat to make sure saa_destroy_pixmap happens
    before damageDestroyPixmap and destroy the damage object in saa_destroy_pixmap.
    Also add a damage object destruction notifier callback that clears the
    saa pixmap damage pointer should the damage object destruction accidentally
    happen elsewhere.
    
    This makes sure we don't leak damage objects.
    
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Deepak Rawat <drawat at vmware.com>

commit 53e87117bbf1cba05a5b5046db9efa961b18fc74
Author: Thomas Hellstrom <thellstrom at vmware.com>
Date:   Fri Nov 23 09:30:42 2018 +0100

    vmwgfx: Use libdrm to obtain the drm device node name v2
    
    We were relying on a linux-specific way to do this. Now that the code is
    used also on FreeBSD and there is functionality in libdrm to do this,
    Use that functionality.
    
    v2:
    Remove unused variable warning in the !VMWGFX_LIBDRM_DEVICENAME case.
    
    Co-authored-by: Johannes Lundberg <johalun0 at gmail.com>
    Signed-off-by: Thomas Hellstrom <thellstrom at vmware.com>
    Reviewed-by: Deepak Rawat <drawat at vmware.com> #v1