public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Louis Chauvet <louis.chauvet@bootlin.com>
To: 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>
Cc: thomas.petazzoni@bootlin.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Mark Yacoub <markyacoub@google.com>
Subject: Re: [PATCH v2] drm: writeback: Fix drm_writeback_connector_cleanup signature
Date: Fri, 20 Jun 2025 11:32:16 +0200	[thread overview]
Message-ID: <ce2f3c96-38e4-4a75-9b6c-838e070a274d@bootlin.com> (raw)
In-Reply-To: <20250429-drm-fix-writeback-cleanup-v2-1-548ff3a4e284@bootlin.com>

Hi all,

This patch is pending for 6 weeks, as this is a bug affecting all build 
with CFI and VKMS (the only user of this API), can someone take a look 
and apply it?

Thanks a lot,
Louis Chauvet

Le 29/04/2025 à 10:36, Louis Chauvet a écrit :
> The drm_writeback_connector_cleanup have the signature:
> 
>       static void drm_writeback_connector_cleanup(
> 		struct drm_device *dev,
> 		struct drm_writeback_connector *wb_connector)
> 
> But it is stored and used as a drmres_release_t
> 
>      typedef void (*drmres_release_t)(struct drm_device *dev, void *res);
> 
> While the current code is valid and does not produce any warning, the
> CFI runtime check (CONFIG_CFI_CLANG) can fail because the function
> signature is not the same as drmres_release_t.
> 
> In order to fix this, change the function signature to match what is
> expected by drmres_release_t.
> 
> Fixes: 1914ba2b91ea ("drm: writeback: Create drmm variants for drm_writeback_connector initialization")
> 
> Suggested-by: Mark Yacoub <markyacoub@google.com>
> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
> ---
> Changes in v2:
> - Forgot to update the documentation
> - Link to v1: https://lore.kernel.org/r/20250428-drm-fix-writeback-cleanup-v1-1-e4c723868b73@bootlin.com
> ---
>   drivers/gpu/drm/drm_writeback.c | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c
> index edbeab88ff2b..d983ee85cf13 100644
> --- a/drivers/gpu/drm/drm_writeback.c
> +++ b/drivers/gpu/drm/drm_writeback.c
> @@ -343,17 +343,18 @@ EXPORT_SYMBOL(drm_writeback_connector_init_with_encoder);
>   /**
>    * drm_writeback_connector_cleanup - Cleanup the writeback connector
>    * @dev: DRM device
> - * @wb_connector: Pointer to the writeback connector to clean up
> + * @data: Pointer to the writeback connector to clean up
>    *
>    * This will decrement the reference counter of blobs and destroy properties. It
>    * will also clean the remaining jobs in this writeback connector. Caution: This helper will not
>    * clean up the attached encoder and the drm_connector.
>    */
>   static void drm_writeback_connector_cleanup(struct drm_device *dev,
> -					    struct drm_writeback_connector *wb_connector)
> +					    void *data)
>   {
>   	unsigned long flags;
>   	struct drm_writeback_job *pos, *n;
> +	struct drm_writeback_connector *wb_connector = data;
>   
>   	delete_writeback_properties(dev);
>   	drm_property_blob_put(wb_connector->pixel_formats_blob_ptr);
> @@ -405,7 +406,7 @@ int drmm_writeback_connector_init(struct drm_device *dev,
>   	if (ret)
>   		return ret;
>   
> -	ret = drmm_add_action_or_reset(dev, (void *)drm_writeback_connector_cleanup,
> +	ret = drmm_add_action_or_reset(dev, drm_writeback_connector_cleanup,
>   				       wb_connector);
>   	if (ret)
>   		return ret;
> 
> ---
> base-commit: a22e0051f9eb2281b181218d97f77cebc299310d
> change-id: 20250428-drm-fix-writeback-cleanup-a1179f3b9691
> 
> Best regards,

-- 
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2025-06-20  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29  8:36 [PATCH v2] drm: writeback: Fix drm_writeback_connector_cleanup signature Louis Chauvet
2025-06-20  9:32 ` Louis Chauvet [this message]
2025-06-21 10:44 ` Maíra Canal
2025-06-23  8:14 ` Louis Chauvet

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=ce2f3c96-38e4-4a75-9b6c-838e070a274d@bootlin.com \
    --to=louis.chauvet@bootlin.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=markyacoub@google.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=thomas.petazzoni@bootlin.com \
    --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