From: Danilo Krummrich <dakr@redhat.com>
To: daniel@ffwll.ch, airlied@linux.ie, tzimmermann@suse.de,
mripard@kernel.org, liviu.dudau@arm.com, brian.starkey@arm.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Danilo Krummrich <dakr@redhat.com>
Subject: [PATCH drm-misc-next 8/8] drm/arm/malidp: drv: protect device resources after removal
Date: Fri, 19 Aug 2022 23:25:38 +0200 [thread overview]
Message-ID: <20220819212538.559902-2-dakr@redhat.com> (raw)
In-Reply-To: <20220819212015.556220-1-dakr@redhat.com>
(Hardware) resources which are bound to the driver and device lifecycle
must not be accessed after the device and driver are unbound.
However, the DRM device isn't freed as long as the last user didn't
close it, hence userspace can still call into the driver.
Therefore protect the critical sections which are accessing those
resources with drm_dev_enter() and drm_dev_exit().
Signed-off-by: Danilo Krummrich <dakr@redhat.com>
---
drivers/gpu/drm/arm/malidp_drv.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/arm/malidp_drv.c b/drivers/gpu/drm/arm/malidp_drv.c
index aedd30f5f451..8bb8e8d14461 100644
--- a/drivers/gpu/drm/arm/malidp_drv.c
+++ b/drivers/gpu/drm/arm/malidp_drv.c
@@ -234,9 +234,12 @@ static void malidp_atomic_commit_tail(struct drm_atomic_state *state)
struct malidp_drm *malidp = drm_to_malidp(drm);
struct drm_crtc *crtc;
struct drm_crtc_state *old_crtc_state;
- int i;
+ int i, idx;
bool fence_cookie = dma_fence_begin_signalling();
+ if (!drm_dev_enter(drm, &idx))
+ return;
+
pm_runtime_get_sync(drm->dev);
/*
@@ -267,6 +270,8 @@ static void malidp_atomic_commit_tail(struct drm_atomic_state *state)
pm_runtime_put(drm->dev);
drm_atomic_helper_cleanup_planes(drm, state);
+
+ drm_dev_exit(idx);
}
static const struct drm_mode_config_helper_funcs malidp_mode_config_helpers = {
--
2.37.2
prev parent reply other threads:[~2022-08-19 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 21:20 [PATCH drm-misc-next 0/8] drm/arm/malidp: use drm managed resources Danilo Krummrich
2022-08-19 21:20 ` [PATCH drm-misc-next 1/8] drm/arm/malidp: use drmm_* to allocate driver structures Danilo Krummrich
2022-08-19 21:20 ` [PATCH drm-misc-next 2/8] drm/arm/malidp: replace drm->dev_private with drm_to_malidp() Danilo Krummrich
2022-08-19 21:24 ` [PATCH drm-misc-next 3/8] drm/arm/malidp: crtc: use drmm_crtc_init_with_planes() Danilo Krummrich
2022-08-19 21:24 ` [PATCH drm-misc-next 4/8] drm/arm/malidp: plane: use drm managed resources Danilo Krummrich
2022-08-19 21:24 ` [PATCH drm-misc-next 5/8] drm/arm/malidp: use drm_dev_unplug() Danilo Krummrich
2022-08-19 21:24 ` [PATCH drm-misc-next 6/8] drm/arm/malidp: plane: protect device resources after removal Danilo Krummrich
2022-08-19 21:25 ` [PATCH drm-misc-next 7/8] drm/arm/malidp: crtc: " Danilo Krummrich
2022-08-19 21:25 ` Danilo Krummrich [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=20220819212538.559902-2-dakr@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@linux.ie \
--cc=brian.starkey@arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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