From: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
To: linux-graphics-maintainer@vmware.com, zackr@vmware.com,
airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Cc: gregkh@linuxfoundation.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
skhan@linuxfoundation.org,
Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: [PATCH 0/3] drm, drm/vmwgfx: fixes and updates related to drm_master
Date: Thu, 22 Jul 2021 17:29:26 +0800 [thread overview]
Message-ID: <20210722092929.244629-1-desmondcheongzx@gmail.com> (raw)
Hi,
This series contains some improvements that Daniel Vetter proposed following a discussion on a recent series:
https://lore.kernel.org/lkml/20210712043508.11584-1-desmondcheongzx@gmail.com/
While preparing these patches, I also noticed some unprotected uses of drm_master in the vmwgfx driver that can be addressed by new functions from the previous series.
This series is thus broken up into three patches:
1. Switch from the outer drm_device.master_mutex to the inner drm_file.master_lookup_lock in drm_is_current_master.
2. Update the kerneldoc for lease fields in drm_master to clarify lifetime/locking rules.
3. Prevent potential use-after-free bugs by replacing calls to drm_master_get with drm_file_get_master in vmwgfx_surface.c.
Best wishes,
Desmond
Desmond Cheong Zhi Xi (3):
drm: use the lookup lock in drm_is_current_master
drm: clarify lifetime/locking for drm_master's lease fields
drm/vmwgfx: fix potential UAF in vmwgfx_surface.c
drivers/gpu/drm/drm_auth.c | 9 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 4 +-
include/drm/drm_auth.h | 62 ++++++++++++++++++++-----
3 files changed, 58 insertions(+), 17 deletions(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
To: linux-graphics-maintainer@vmware.com, zackr@vmware.com,
airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Cc: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
intel-gfx@lists.freedesktop.org, skhan@linuxfoundation.org,
gregkh@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: [PATCH 0/3] drm, drm/vmwgfx: fixes and updates related to drm_master
Date: Thu, 22 Jul 2021 17:29:26 +0800 [thread overview]
Message-ID: <20210722092929.244629-1-desmondcheongzx@gmail.com> (raw)
Hi,
This series contains some improvements that Daniel Vetter proposed following a discussion on a recent series:
https://lore.kernel.org/lkml/20210712043508.11584-1-desmondcheongzx@gmail.com/
While preparing these patches, I also noticed some unprotected uses of drm_master in the vmwgfx driver that can be addressed by new functions from the previous series.
This series is thus broken up into three patches:
1. Switch from the outer drm_device.master_mutex to the inner drm_file.master_lookup_lock in drm_is_current_master.
2. Update the kerneldoc for lease fields in drm_master to clarify lifetime/locking rules.
3. Prevent potential use-after-free bugs by replacing calls to drm_master_get with drm_file_get_master in vmwgfx_surface.c.
Best wishes,
Desmond
Desmond Cheong Zhi Xi (3):
drm: use the lookup lock in drm_is_current_master
drm: clarify lifetime/locking for drm_master's lease fields
drm/vmwgfx: fix potential UAF in vmwgfx_surface.c
drivers/gpu/drm/drm_auth.c | 9 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 4 +-
include/drm/drm_auth.h | 62 ++++++++++++++++++++-----
3 files changed, 58 insertions(+), 17 deletions(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
To: linux-graphics-maintainer@vmware.com, zackr@vmware.com,
airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: [PATCH 0/3] drm, drm/vmwgfx: fixes and updates related to drm_master
Date: Thu, 22 Jul 2021 17:29:26 +0800 [thread overview]
Message-ID: <20210722092929.244629-1-desmondcheongzx@gmail.com> (raw)
Hi,
This series contains some improvements that Daniel Vetter proposed following a discussion on a recent series:
https://lore.kernel.org/lkml/20210712043508.11584-1-desmondcheongzx@gmail.com/
While preparing these patches, I also noticed some unprotected uses of drm_master in the vmwgfx driver that can be addressed by new functions from the previous series.
This series is thus broken up into three patches:
1. Switch from the outer drm_device.master_mutex to the inner drm_file.master_lookup_lock in drm_is_current_master.
2. Update the kerneldoc for lease fields in drm_master to clarify lifetime/locking rules.
3. Prevent potential use-after-free bugs by replacing calls to drm_master_get with drm_file_get_master in vmwgfx_surface.c.
Best wishes,
Desmond
Desmond Cheong Zhi Xi (3):
drm: use the lookup lock in drm_is_current_master
drm: clarify lifetime/locking for drm_master's lease fields
drm/vmwgfx: fix potential UAF in vmwgfx_surface.c
drivers/gpu/drm/drm_auth.c | 9 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 4 +-
include/drm/drm_auth.h | 62 ++++++++++++++++++++-----
3 files changed, 58 insertions(+), 17 deletions(-)
--
2.25.1
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
WARNING: multiple messages have this Message-ID (diff)
From: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
To: linux-graphics-maintainer@vmware.com, zackr@vmware.com,
airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Cc: gregkh@linuxfoundation.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
skhan@linuxfoundation.org,
Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: [Intel-gfx] [PATCH 0/3] drm, drm/vmwgfx: fixes and updates related to drm_master
Date: Thu, 22 Jul 2021 17:29:26 +0800 [thread overview]
Message-ID: <20210722092929.244629-1-desmondcheongzx@gmail.com> (raw)
Hi,
This series contains some improvements that Daniel Vetter proposed following a discussion on a recent series:
https://lore.kernel.org/lkml/20210712043508.11584-1-desmondcheongzx@gmail.com/
While preparing these patches, I also noticed some unprotected uses of drm_master in the vmwgfx driver that can be addressed by new functions from the previous series.
This series is thus broken up into three patches:
1. Switch from the outer drm_device.master_mutex to the inner drm_file.master_lookup_lock in drm_is_current_master.
2. Update the kerneldoc for lease fields in drm_master to clarify lifetime/locking rules.
3. Prevent potential use-after-free bugs by replacing calls to drm_master_get with drm_file_get_master in vmwgfx_surface.c.
Best wishes,
Desmond
Desmond Cheong Zhi Xi (3):
drm: use the lookup lock in drm_is_current_master
drm: clarify lifetime/locking for drm_master's lease fields
drm/vmwgfx: fix potential UAF in vmwgfx_surface.c
drivers/gpu/drm/drm_auth.c | 9 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 4 +-
include/drm/drm_auth.h | 62 ++++++++++++++++++++-----
3 files changed, 58 insertions(+), 17 deletions(-)
--
2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-07-22 9:30 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 9:29 Desmond Cheong Zhi Xi [this message]
2021-07-22 9:29 ` [Intel-gfx] [PATCH 0/3] drm, drm/vmwgfx: fixes and updates related to drm_master Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [PATCH 1/3] drm: use the lookup lock in drm_is_current_master Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 10:38 ` Daniel Vetter
2021-07-22 10:38 ` [Intel-gfx] " Daniel Vetter
2021-07-22 10:38 ` Daniel Vetter
2021-07-22 10:38 ` Daniel Vetter
2021-07-22 15:04 ` Boqun Feng
2021-07-22 15:04 ` [Intel-gfx] " Boqun Feng
2021-07-22 15:04 ` Boqun Feng
2021-07-22 19:02 ` Daniel Vetter
2021-07-22 19:02 ` Daniel Vetter
2021-07-22 19:02 ` Daniel Vetter
2021-07-22 19:02 ` [Intel-gfx] " Daniel Vetter
2021-07-23 7:16 ` Boqun Feng
2021-07-23 7:16 ` [Intel-gfx] " Boqun Feng
2021-07-23 7:16 ` Boqun Feng
2021-07-27 14:37 ` Peter Zijlstra
2021-07-27 14:37 ` [Intel-gfx] " Peter Zijlstra
2021-07-27 14:37 ` Peter Zijlstra
2021-07-29 7:00 ` Daniel Vetter
2021-07-29 7:00 ` Daniel Vetter
2021-07-29 7:00 ` Daniel Vetter
2021-07-29 7:00 ` [Intel-gfx] " Daniel Vetter
2021-07-29 14:32 ` Desmond Cheong Zhi Xi
2021-07-29 14:32 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-29 14:32 ` Desmond Cheong Zhi Xi
2021-07-29 14:32 ` Desmond Cheong Zhi Xi
2021-07-29 14:45 ` [Intel-gfx] " Peter Zijlstra
2021-07-29 14:45 ` Peter Zijlstra
2021-07-29 14:45 ` Peter Zijlstra
2021-07-29 14:45 ` Peter Zijlstra
2021-07-22 9:29 ` [PATCH 2/3] drm: clarify lifetime/locking for drm_master's lease fields Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 10:35 ` Daniel Vetter
2021-07-22 10:35 ` [Intel-gfx] " Daniel Vetter
2021-07-22 10:35 ` Daniel Vetter
2021-07-22 10:35 ` Daniel Vetter
2021-07-22 13:02 ` Desmond Cheong Zhi Xi
2021-07-22 13:02 ` Desmond Cheong Zhi Xi
2021-07-22 13:02 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 13:02 ` Desmond Cheong Zhi Xi
2021-07-22 14:17 ` Daniel Vetter
2021-07-22 14:17 ` Daniel Vetter
2021-07-22 14:17 ` Daniel Vetter
2021-07-22 14:17 ` [Intel-gfx] " Daniel Vetter
2021-07-22 9:29 ` [PATCH 3/3] drm/vmwgfx: fix potential UAF in vmwgfx_surface.c Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 10:39 ` Daniel Vetter
2021-07-22 10:39 ` [Intel-gfx] " Daniel Vetter
2021-07-22 10:39 ` Daniel Vetter
2021-07-22 10:39 ` Daniel Vetter
2021-07-22 19:17 ` Zack Rusin
2021-07-22 19:17 ` Zack Rusin
2021-07-22 19:17 ` Zack Rusin
2021-07-22 19:17 ` [Intel-gfx] " Zack Rusin
2021-07-23 6:44 ` Desmond Cheong Zhi Xi
2021-07-23 6:44 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-23 6:44 ` Desmond Cheong Zhi Xi
2021-07-23 6:44 ` Desmond Cheong Zhi Xi
2021-07-22 14:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm, drm/vmwgfx: fixes and updates related to drm_master Patchwork
2021-07-22 14:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-07-27 17:42 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm, drm/vmwgfx: fixes and updates related to drm_master (rev2) Patchwork
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=20210722092929.244629-1-desmondcheongzx@gmail.com \
--to=desmondcheongzx@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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.