From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH][next] drm/omap: clean up error exit path on omap_encoder allocation failure
Date: Mon, 28 Oct 2024 10:28:06 +0200 [thread overview]
Message-ID: <3ecf364c-8bb1-4f96-817e-fd36a2c29c84@ideasonboard.com> (raw)
In-Reply-To: <20241015141012.155559-1-colin.i.king@gmail.com>
Hi,
On 15/10/2024 17:10, Colin Ian King wrote:
> Currently when an allocation failure occurs for omap_encoder the exit
> path will destroy encoder via omap_encoder_destroy if it is not null.
> However, encoder is always null at this point, so the check and destroy
> is redundant and can be removed. Clean up the code by removing the exit
> path and redundant omap_encoder_destroy call, and just return NULL.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/gpu/drm/omapdrm/omap_encoder.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
This is correct, but I think it would make sense to fix the error
handling in omap_encoder_init() fully, instead of just partially:
drm_encoder_init() can return an error, in which case we should free the
omap_encoder.
Could you update the patch to do that too?
Tomi
> diff --git a/drivers/gpu/drm/omapdrm/omap_encoder.c b/drivers/gpu/drm/omapdrm/omap_encoder.c
> index 4dd05bc732da..a99022638a2c 100644
> --- a/drivers/gpu/drm/omapdrm/omap_encoder.c
> +++ b/drivers/gpu/drm/omapdrm/omap_encoder.c
> @@ -126,21 +126,15 @@ struct drm_encoder *omap_encoder_init(struct drm_device *dev,
>
> omap_encoder = kzalloc(sizeof(*omap_encoder), GFP_KERNEL);
> if (!omap_encoder)
> - goto fail;
> + return NULL;
>
> omap_encoder->output = output;
>
> encoder = &omap_encoder->base;
>
> drm_encoder_init(dev, encoder, &omap_encoder_funcs,
> DRM_MODE_ENCODER_TMDS, NULL);
> drm_encoder_helper_add(encoder, &omap_encoder_helper_funcs);
>
> return encoder;
> -
> -fail:
> - if (encoder)
> - omap_encoder_destroy(encoder);
> -
> - return NULL;
> }
prev parent reply other threads:[~2024-10-28 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 14:10 Colin Ian King
2024-10-28 8:28 ` Tomi Valkeinen [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=3ecf364c-8bb1-4f96-817e-fd36a2c29c84@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=colin.i.king@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®