From: Jani Nikula <jani.nikula@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3] drm/i915: Warn on if set frontbuffer return value is not NULL on release
Date: Thu, 28 Sep 2023 11:56:56 +0300 [thread overview]
Message-ID: <871qeik753.fsf@intel.com> (raw)
In-Reply-To: <20230928082924.164720-1-jouni.hogander@intel.com>
On Thu, 28 Sep 2023, Jouni Högander <jouni.hogander@intel.com> wrote:
> i915_gem_object_set_frontbuffer returns set frontbuffer pointer. When we
> are releasing frontbuffer we are clearing the pointer from the object. Warn
> on if return value is not null.
>
> v3: Check i915_gem_object_set_frontbuffer return value separately
> v2: Instead of ignoring do drm_WARN_ON
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_frontbuffer.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_frontbuffer.c b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> index d5540c739404..412a19a888a2 100644
> --- a/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> +++ b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> @@ -251,7 +251,7 @@ static void frontbuffer_retire(struct i915_active *ref)
> static void frontbuffer_release(struct kref *ref)
> __releases(&intel_bo_to_i915(front->obj)->display.fb_tracking.lock)
> {
> - struct intel_frontbuffer *front =
> + struct intel_frontbuffer *ret, *front =
> container_of(ref, typeof(*front), ref);
> struct drm_i915_gem_object *obj = front->obj;
>
> @@ -259,7 +259,8 @@ static void frontbuffer_release(struct kref *ref)
>
> i915_ggtt_clear_scanout(obj);
>
> - i915_gem_object_set_frontbuffer(obj, NULL);
> + ret = i915_gem_object_set_frontbuffer(obj, NULL);
> + drm_WARN_ON(&intel_bo_to_i915(obj)->drm, ret);
> spin_unlock(&intel_bo_to_i915(obj)->display.fb_tracking.lock);
>
> i915_active_fini(&front->write);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-09-28 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 8:29 [Intel-gfx] [PATCH v3] drm/i915: Warn on if set frontbuffer return value is not NULL on release Jouni Högander
2023-09-28 8:56 ` Jani Nikula [this message]
2023-09-29 7:37 ` Hogander, Jouni
2023-09-28 9:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Warn on if set frontbuffer return value is not NULL on release (rev2) Patchwork
2023-09-28 18:44 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-29 7:28 ` Hogander, Jouni
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=871qeik753.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jouni.hogander@intel.com \
--cc=rodrigo.vivi@intel.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