From: "Tauro, Riana" <riana.tauro@intel.com>
To: Raag Jadav <raag.jadav@intel.com>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <netdev@vger.kernel.org>
Cc: <rodrigo.vivi@intel.com>, <dev@lankhorst.se>, <airlied@gmail.com>,
<simona@ffwll.ch>, <kuba@kernel.org>
Subject: Re: [PATCH v2 3/4] drm/xe/drm_ras: Add per node cleanup action
Date: Mon, 1 Jun 2026 14:43:58 +0530 [thread overview]
Message-ID: <9039cade-614c-4410-a689-26008fa94776@intel.com> (raw)
In-Reply-To: <20260523050212.557292-4-raag.jadav@intel.com>
On 5/23/2026 10:30 AM, Raag Jadav wrote:
> cleanup_node_param() is not registered for previous node in case of counter
> allocation failure, which results in stale memory of previous node that
> isn't cleaned up on unwind. Add per node cleanup action which guarantees
> cleanup on unwind and also simplifies the cleanup logic.
>
> Fixes: b40db12b542f ("drm/xe/xe_drm_ras: Add support for XE DRM RAS")
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_drm_ras.c | 59 +++++++++++++--------------------
> 1 file changed, 23 insertions(+), 36 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_drm_ras.c b/drivers/gpu/drm/xe/xe_drm_ras.c
> index c1d5ac198a7c..b901976203fc 100644
> --- a/drivers/gpu/drm/xe/xe_drm_ras.c
> +++ b/drivers/gpu/drm/xe/xe_drm_ras.c
> @@ -131,53 +131,46 @@ static int assign_node_params(struct xe_device *xe, struct drm_ras_node *node,
> return 0;
> }
>
> -static void cleanup_node_param(struct xe_drm_ras *ras, const enum drm_xe_ras_error_severity severity)
> +static void cleanup_node_param(struct drm_ras_node *node)
> {
> - struct drm_ras_node *node = &ras->node[severity];
> -
> - ras->info[severity] = NULL;
> -
> kfree(node->device_name);
> node->device_name = NULL;
> }
>
> +static void cleanup_node(struct drm_device *drm, void *node)
> +{
> + drm_ras_node_unregister(node);
> + cleanup_node_param(node);
> +}
> +
> static int register_nodes(struct xe_device *xe)
> {
> struct xe_drm_ras *ras = &xe->ras;
> - int i;
> + struct drm_ras_node *node;
> + int i, ret;
>
> for_each_error_severity(i) {
> - struct drm_ras_node *node = &ras->node[i];
> - int ret;
> + node = &ras->node[i];
>
> ret = assign_node_params(xe, node, i);
> - if (ret) {
> - cleanup_node_param(ras, i);
> - return ret;
> - }
> + if (ret)
> + break;
>
> ret = drm_ras_node_register(node);
> - if (ret) {
> - cleanup_node_param(ras, i);
> - return ret;
> - }
> - }
> -
> - return 0;
> -}
> -
> -static void xe_drm_ras_unregister_nodes(struct drm_device *device, void *arg)
> -{
> - struct xe_device *xe = arg;
> - struct xe_drm_ras *ras = &xe->ras;
> - int i;
> + if (ret)
> + break;
>
> - for_each_error_severity(i) {
> - struct drm_ras_node *node = &ras->node[i];
> + ret = drmm_add_action_or_reset(&xe->drm, cleanup_node, node);
> + if (ret)
> + break;
On failure of drmm_add_action_or_reset , action is called. We don't need
to cleanup_node_param again Thanks Riana
> + }
>
> - drm_ras_node_unregister(node);
> - cleanup_node_param(ras, i);
> + if (ret) {
> + cleanup_node_param(node);
> + ras->info[i] = NULL;
> }
> +
> + return ret;
> }
>
> /**
> @@ -206,11 +199,5 @@ int xe_drm_ras_init(struct xe_device *xe)
> return err;
> }
>
> - err = drmm_add_action_or_reset(&xe->drm, xe_drm_ras_unregister_nodes, xe);
> - if (err) {
> - drm_err(&xe->drm, "Failed to add action for Xe DRM RAS (%pe)\n", ERR_PTR(err));
> - return err;
> - }
> -
> return 0;
> }
next prev parent reply other threads:[~2026-06-01 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 5:00 [PATCH v2 0/4] DRM RAS Fixes Raag Jadav
2026-05-23 5:00 ` [PATCH v2 1/4] drm/ras: Cancel and free message on get counter failure Raag Jadav
2026-05-25 9:53 ` Tauro, Riana
2026-05-23 5:00 ` [PATCH v2 2/4] drm/xe/drm_ras: Make counter allocation drm managed Raag Jadav
2026-05-23 5:00 ` [PATCH v2 3/4] drm/xe/drm_ras: Add per node cleanup action Raag Jadav
2026-06-01 9:13 ` Tauro, Riana [this message]
2026-05-23 5:00 ` [PATCH v2 4/4] drm/xe/hw_error: Use HW_ERR prefix in log Raag Jadav
2026-06-01 9:19 ` Tauro, Riana
2026-06-01 11:13 ` Michal Wajdeczko
2026-06-01 12:25 ` Raag Jadav
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=9039cade-614c-4410-a689-26008fa94776@intel.com \
--to=riana.tauro@intel.com \
--cc=airlied@gmail.com \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raag.jadav@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
/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