From: Jocelyn Falempe <jfalempe@redhat.com>
To: zack.rusin@broadcom.com, stable@vger.kernel.org,
dri-devel@lists.freedesktop.org
Cc: Jocelyn Falempe <jfalempe@redhat.com>
Subject: [PATCH 0/2] drm/vmwgfx backport two fixes to v6.1.x branch
Date: Mon, 22 Jan 2024 18:10:11 +0100 [thread overview]
Message-ID: <20240122172031.243604-1-jfalempe@redhat.com> (raw)
Hi,
I've backported this two commits:
f9e96bf19054 drm/vmwgfx: Fix possible invalid drm gem put calls
91398b413d03 drm/vmwgfx: Keep a gem reference to user bos in surfaces
They both fixes a950b989ea29 ("drm/vmwgfx: Do not drop the reference
to the handle too soon")
which has been backported to v6.1.x branch as 0a127ac97240
There was a lot of conflicts, and as I'm not familiar with the vmwgfx
driver, it's better to review and test them.
I've run a short test, and it worked, but that's certainly not enough.
Thanks,
Zack Rusin (2):
drm/vmwgfx: Fix possible invalid drm gem put calls
drm/vmwgfx: Keep a gem reference to user bos in surfaces
drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 7 ++----
drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c | 8 +++----
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 20 ++++++++++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 12 +++++------
drivers/gpu/drm/vmwgfx/vmwgfx_gem.c | 24 ++++++++++++++++-----
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 10 ++++-----
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | 3 +--
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 18 ++++++++--------
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 5 ++---
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 27 +++++++-----------------
10 files changed, 75 insertions(+), 59 deletions(-)
base-commit: fec3b1451d5febbc9e04250f879c10f8952e6bed
--
2.43.0
next reply other threads:[~2024-01-22 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 17:10 Jocelyn Falempe [this message]
2024-01-22 17:10 ` [PATCH 1/2] drm/vmwgfx: Fix possible invalid drm gem put calls Jocelyn Falempe
2024-01-22 17:10 ` [PATCH 2/2] drm/vmwgfx: Keep a gem reference to user bos in surfaces Jocelyn Falempe
2024-01-22 19:01 ` [PATCH 0/2] drm/vmwgfx backport two fixes to v6.1.x branch Greg KH
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=20240122172031.243604-1-jfalempe@redhat.com \
--to=jfalempe@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=zack.rusin@broadcom.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