From: Jani Nikula <jani.nikula@linux.intel.com>
To: Haoxiang Li <haoxiang_li2024@163.com>,
rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com,
tursulin@ursulin.net, airlied@gmail.com, simona@ffwll.ch,
gustavo.sousa@intel.com
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Haoxiang Li <haoxiang_li2024@163.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] drm/i915/display: Add check for alloc_ordered_workqueue() and alloc_workqueue()
Date: Fri, 16 May 2025 15:21:15 +0300 [thread overview]
Message-ID: <87cyc8wxtw.fsf@intel.com> (raw)
In-Reply-To: <20250424025539.3504019-1-haoxiang_li2024@163.com>
On Thu, 24 Apr 2025, Haoxiang Li <haoxiang_li2024@163.com> wrote:
> Add check for the return value of alloc_ordered_workqueue()
> and alloc_workqueue(). Furthermore, if some allocations fail,
> cleanup works are added to avoid potential memory leak problem.
>
> Fixes: 40053823baad ("drm/i915/display: move modeset probe/remove functions to intel_display_driver.c")
> Cc: stable@vger.kernel.org
> Signed-off-by: Haoxiang Li <haoxiang_li2024@163.com>
This patch seems to have been neglected, apologies.
I've rebased it and included it as part of a bigger series [1].
Thanks for the patch.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1747397638.git.jani.nikula@intel.com
> ---
> Changes in v2:
> - Split the compound conditional statement into separate
> conditional statements to facilitate cleanup works.
> - Add cleanup works to destory work queues if allocations fail,
> and modify the later goto destination to do the full excercise.
> - modify the patch description. Thanks, Jani!
> ---
> .../drm/i915/display/intel_display_driver.c | 30 +++++++++++++++----
> 1 file changed, 25 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_driver.c b/drivers/gpu/drm/i915/display/intel_display_driver.c
> index 31740a677dd8..ac94561715dc 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_driver.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_driver.c
> @@ -241,31 +241,45 @@ int intel_display_driver_probe_noirq(struct intel_display *display)
> intel_dmc_init(display);
>
> display->wq.modeset = alloc_ordered_workqueue("i915_modeset", 0);
> + if (!display->wq.modeset) {
> + ret = -ENOMEM;
> + goto cleanup_vga_client_pw_domain_dmc;
> + }
> +
> display->wq.flip = alloc_workqueue("i915_flip", WQ_HIGHPRI |
> WQ_UNBOUND, WQ_UNBOUND_MAX_ACTIVE);
> + if (!display->wq.flip) {
> + ret = -ENOMEM;
> + goto cleanup_wq_modeset;
> + }
> +
> display->wq.cleanup = alloc_workqueue("i915_cleanup", WQ_HIGHPRI, 0);
> + if (!display->wq.cleanup) {
> + ret = -ENOMEM;
> + goto cleanup_wq_flip;
> + }
>
> intel_mode_config_init(display);
>
> ret = intel_cdclk_init(display);
> if (ret)
> - goto cleanup_vga_client_pw_domain_dmc;
> + goto cleanup_wq_cleanup;
>
> ret = intel_color_init(display);
> if (ret)
> - goto cleanup_vga_client_pw_domain_dmc;
> + goto cleanup_wq_cleanup;
>
> ret = intel_dbuf_init(i915);
> if (ret)
> - goto cleanup_vga_client_pw_domain_dmc;
> + goto cleanup_wq_cleanup;
>
> ret = intel_bw_init(i915);
> if (ret)
> - goto cleanup_vga_client_pw_domain_dmc;
> + goto cleanup_wq_cleanup;
>
> ret = intel_pmdemand_init(display);
> if (ret)
> - goto cleanup_vga_client_pw_domain_dmc;
> + goto cleanup_wq_cleanup;
>
> intel_init_quirks(display);
>
> @@ -273,6 +287,12 @@ int intel_display_driver_probe_noirq(struct intel_display *display)
>
> return 0;
>
> +cleanup_wq_cleanup:
> + destroy_workqueue(display->wq.cleanup);
> +cleanup_wq_flip:
> + destroy_workqueue(display->wq.flip);
> +cleanup_wq_modeset:
> + destroy_workqueue(display->wq.modeset);
> cleanup_vga_client_pw_domain_dmc:
> intel_dmc_fini(display);
> intel_power_domains_driver_remove(display);
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-05-16 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 2:55 [PATCH v2 RESEND] drm/i915/display: Add check for alloc_ordered_workqueue() and alloc_workqueue() Haoxiang Li
2025-05-16 12:21 ` Jani Nikula [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=87cyc8wxtw.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.sousa@intel.com \
--cc=haoxiang_li2024@163.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tursulin@ursulin.net \
/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