From: Jocelyn Falempe <jfalempe@redhat.com>
To: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com,
"Maarten Lankhorst" <dev@lankhorst.se>,
"Michał Grzelak" <michal.grzelak@intel.com>
Subject: Re: [PATCH v2] drm/i915/panic: fix panic structure allocation memory leak
Date: Wed, 15 Oct 2025 14:54:02 +0200 [thread overview]
Message-ID: <7e48cc48-564f-486e-b6b3-8fa95068387a@redhat.com> (raw)
In-Reply-To: <20251015095135.2183415-1-jani.nikula@intel.com>
On 15/10/2025 11:51, Jani Nikula wrote:
> Separating the panic allocation from framebuffer allocation in commit
> 729c5f7ffa83 ("drm/{i915,xe}/panic: move framebuffer allocation where it
> belongs") failed to deallocate the panic structure anywhere.
>
> The fix is two-fold. First, free the panic structure in
> intel_user_framebuffer_destroy() in the general case. Second, move the
> panic allocation later to intel_framebuffer_init() to not leak the panic
> structure in error paths (if any, now or later) between
> intel_framebuffer_alloc() and intel_framebuffer_init().
>
Thanks, it looks good to me.
Reviewed-by: Jocelyn Falempe <jfalempe@redhat.com>
> v2: Rebase
>
> Fixes: 729c5f7ffa83 ("drm/{i915,xe}/panic: move framebuffer allocation where it belongs")
> Cc: Jocelyn Falempe <jfalempe@redhat.com>
> Cc: Maarten Lankhorst <dev@lankhorst.se>
> Reported-by: Michał Grzelak <michal.grzelak@intel.com>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Tested-by: Michał Grzelak <michal.grzelak@intel.com> # v1
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_fb.c | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fb.c b/drivers/gpu/drm/i915/display/intel_fb.c
> index 9c256a2805e4..3958628c73e9 100644
> --- a/drivers/gpu/drm/i915/display/intel_fb.c
> +++ b/drivers/gpu/drm/i915/display/intel_fb.c
> @@ -2114,6 +2114,7 @@ static void intel_user_framebuffer_destroy(struct drm_framebuffer *fb)
>
> intel_frontbuffer_put(intel_fb->frontbuffer);
>
> + kfree(intel_fb->panic);
> kfree(intel_fb);
> }
>
> @@ -2212,16 +2213,22 @@ int intel_framebuffer_init(struct intel_framebuffer *intel_fb,
> struct intel_display *display = to_intel_display(obj->dev);
> struct drm_framebuffer *fb = &intel_fb->base;
> u32 max_stride;
> - int ret = -EINVAL;
> + int ret;
> int i;
>
> + intel_fb->panic = intel_panic_alloc();
> + if (!intel_fb->panic)
> + return -ENOMEM;
> +
> /*
> * intel_frontbuffer_get() must be done before
> * intel_fb_bo_framebuffer_init() to avoid set_tiling vs. addfb race.
> */
> intel_fb->frontbuffer = intel_frontbuffer_get(obj);
> - if (!intel_fb->frontbuffer)
> - return -ENOMEM;
> + if (!intel_fb->frontbuffer) {
> + ret = -ENOMEM;
> + goto err_free_panic;
> + }
>
> ret = intel_fb_bo_framebuffer_init(obj, mode_cmd);
> if (ret)
> @@ -2320,6 +2327,9 @@ int intel_framebuffer_init(struct intel_framebuffer *intel_fb,
> intel_fb_bo_framebuffer_fini(obj);
> err_frontbuffer_put:
> intel_frontbuffer_put(intel_fb->frontbuffer);
> +err_free_panic:
> + kfree(intel_fb->panic);
> +
> return ret;
> }
>
> @@ -2346,20 +2356,11 @@ intel_user_framebuffer_create(struct drm_device *dev,
> struct intel_framebuffer *intel_framebuffer_alloc(void)
> {
> struct intel_framebuffer *intel_fb;
> - struct intel_panic *panic;
>
> intel_fb = kzalloc(sizeof(*intel_fb), GFP_KERNEL);
> if (!intel_fb)
> return NULL;
>
> - panic = intel_panic_alloc();
> - if (!panic) {
> - kfree(intel_fb);
> - return NULL;
> - }
> -
> - intel_fb->panic = panic;
> -
> return intel_fb;
> }
>
next prev parent reply other threads:[~2025-10-15 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 9:51 [PATCH v2] drm/i915/panic: fix panic structure allocation memory leak Jani Nikula
2025-10-15 11:20 ` ✓ i915.CI.BAT: success for drm/i915/panic: fix panic structure allocation memory leak (rev2) Patchwork
2025-10-15 12:54 ` Jocelyn Falempe [this message]
2025-10-15 17:39 ` ✗ i915.CI.Full: failure " 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=7e48cc48-564f-486e-b6b3-8fa95068387a@redhat.com \
--to=jfalempe@redhat.com \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=michal.grzelak@intel.com \
--cc=ville.syrjala@linux.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