From: Thomas Zimmermann <tzimmermann@suse.de>
To: Triet Hoang <triet.hoang.dev@gmail.com>,
maarten.lankhorst@linux.intel.com
Cc: mripard@kernel.org, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/gem: Handle shadow plane state allocation failure
Date: Mon, 17 Aug 2026 08:37:17 +0200 [thread overview]
Message-ID: <90771e15-fa75-4915-a681-709c6010d998@suse.de> (raw)
In-Reply-To: <20260816165852.44558-1-triet.hoang.dev@gmail.com>
Hi,
the whole reset mechanism has never worked well IMHO. Maxime currently
reworks it entirely. Not sure if we meanwhile want to paper over the
reset issue.
Best regards
Thomas
Am 16.08.26 um 18:58 schrieb Triet Hoang:
> Allocate the new shadow plane state before destroying the existing
> state, so that an allocation failure leaves the current state intact.
>
> Signed-off-by: Triet Hoang <triet.hoang.dev@gmail.com>
> ---
> drivers/gpu/drm/drm_gem_atomic_helper.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gem_atomic_helper.c b/drivers/gpu/drm/drm_gem_atomic_helper.c
> index abef865c5..24a0b9398 100644
> --- a/drivers/gpu/drm/drm_gem_atomic_helper.c
> +++ b/drivers/gpu/drm/drm_gem_atomic_helper.c
> @@ -308,14 +308,16 @@ EXPORT_SYMBOL(__drm_gem_reset_shadow_plane);
> */
> void drm_gem_reset_shadow_plane(struct drm_plane *plane)
> {
> - struct drm_shadow_plane_state *shadow_plane_state;
> + struct drm_shadow_plane_state *shadow_plane_state = kzalloc_obj(*shadow_plane_state);
> +
> + if (!shadow_plane_state)
> + return;
>
> if (plane->state) {
> drm_gem_destroy_shadow_plane_state(plane, plane->state);
> plane->state = NULL; /* must be set to NULL here */
> }
>
> - shadow_plane_state = kzalloc_obj(*shadow_plane_state);
> __drm_gem_reset_shadow_plane(plane, shadow_plane_state);
> }
> EXPORT_SYMBOL(drm_gem_reset_shadow_plane);
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2026-08-17 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 16:58 Triet Hoang
2026-08-17 6:37 ` Thomas Zimmermann [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=90771e15-fa75-4915-a681-709c6010d998@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=triet.hoang.dev@gmail.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
all inboxes | Powered by JetHome®