All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>,
	dri-devel@lists.freedesktop.org, kernel-dev@igalia.com,
	David Airlie <airlied@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>, Melissa Wen <mwen@igalia.com>,
	Simona Vetter <simona@ffwll.ch>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: sashiko-bot@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v4] drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
Date: Fri, 11 Sep 2026 16:43:44 +0200	[thread overview]
Message-ID: <d3cb37a3-7e79-47bd-a27c-3afe76c05b03@web.de> (raw)
In-Reply-To: <20260826-drm_pending_vblank_event_leak-v4-1-f8de8b996b9d@igalia.com>

> +++ b/drivers/gpu/drm/drm_atomic_uapi.c
> @@ -1458,10 +1458,12 @@ static int prepare_signaling(struct drm_device *dev,
>  			struct dma_fence *fence;
>  			struct drm_out_fence_state *f;
>  
> +			ret = -ENOMEM;
> +

How do you think about to refine the source code a bit more?

I imagine that this assignment statement can be moved behind an additional label
like e_nomem.


>  			f = krealloc(*fence_state, sizeof(**fence_state) *
>  				     (*num_fences + 1), GFP_KERNEL);
>  			if (!f)
> -				return -ENOMEM;
> +				goto err_free_event;
>  
>  			memset(&f[*num_fences], 0, sizeof(*f));
>  


…
> @@ -1531,6 +1533,11 @@ static int prepare_signaling(struct drm_device *dev,
>  	}
>  
>  	return 0;
> +
> +err_free_event:
> +	drm_event_cancel_free(dev, &crtc_state->event->base);

+err_reset_event:

Would you like to avoid a bit of duplicate source code from an other if branch?
https://elixir.bootlin.com/linux/v7.3-rc1/source/drivers/gpu/drm/drm_atomic_uapi.c#L1457-L1461

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v7.3-rc2#n572


> +	crtc_state->event = NULL;
> +	return ret;
>  }


Regards,
Markus

      parent reply	other threads:[~2026-09-11 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 11:46 [PATCH v4] drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr Thadeu Lima de Souza Cascardo
2026-09-11 13:58 ` Melissa Wen
2026-09-11 14:26   ` Melissa Wen
2026-09-11 14:43 ` Markus Elfring [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=d3cb37a3-7e79-47bd-a27c-3afe76c05b03@web.de \
    --to=markus.elfring@web.de \
    --cc=airlied@gmail.com \
    --cc=cascardo@igalia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-dev@igalia.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=mwen@igalia.com \
    --cc=sashiko-bot@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.