Linux USB
 help / color / mirror / Atom feed
* [PATCH] usb: gadget: f_fs: Remove deprecated dma_fence->ops
@ 2026-10-29 12:51 Philipp Stanner
  2026-10-29 13:02 ` sashiko-bot
  2026-10-29 13:19 ` Paul Cercueil
  0 siblings, 2 replies; 3+ messages in thread
From: Philipp Stanner @ 2026-10-29 12:51 UTC (permalink / raw)
  To: Neill Kapron, Greg Kroah-Hartman, Sumit Semwal,
	Christian König, Philipp Stanner, Al Viro, Paul Cercueil,
	Nuno Sá, Sam Day, Michael Bommarito, Gabriel Prostitis
  Cc: linux-usb, linux-kernel, linux-media, dri-devel

The dma_fence_ops function ops->release() has been deprecated because it
prevents drivers from unloading. f_fs's implementation merely frees the
fence. The dma_fence backend performs this deallocation automatically in
the correct manner if ops->release() is not implemented.

The backend simultaneously correctly frees struct ffs_dma_fence since
struct dma_fence is its base class.

Remove ops->release().

Signed-off-by: Philipp Stanner <phasta@kernel.org>
---
 drivers/usb/gadget/function/f_fs.c | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c
index c64a268e98a4..e8672b37e890 100644
--- a/drivers/usb/gadget/function/f_fs.c
+++ b/drivers/usb/gadget/function/f_fs.c
@@ -1479,18 +1479,9 @@ static const char *ffs_dmabuf_get_timeline_name(struct dma_fence *fence)
 	return "";
 }
 
-static void ffs_dmabuf_fence_release(struct dma_fence *fence)
-{
-	struct ffs_dma_fence *dma_fence =
-		container_of(fence, struct ffs_dma_fence, base);
-
-	kfree(dma_fence);
-}
-
 static const struct dma_fence_ops ffs_dmabuf_fence_ops = {
 	.get_driver_name	= ffs_dmabuf_get_driver_name,
 	.get_timeline_name	= ffs_dmabuf_get_timeline_name,
-	.release		= ffs_dmabuf_fence_release,
 };
 
 static int ffs_dma_resv_lock(struct dma_buf *dmabuf, bool nonblock)
-- 
2.56.0


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] usb: gadget: f_fs: Remove deprecated dma_fence->ops
  2026-10-29 12:51 [PATCH] usb: gadget: f_fs: Remove deprecated dma_fence->ops Philipp Stanner
@ 2026-10-29 13:02 ` sashiko-bot
  2026-10-29 13:19 ` Paul Cercueil
  1 sibling, 0 replies; 3+ messages in thread
From: sashiko-bot @ 2026-10-29 13:02 UTC (permalink / raw)
  To: Philipp Stanner; +Cc: linux-usb

> The dma_fence_ops function ops->release() has been deprecated because it
> prevents drivers from unloading. f_fs's implementation merely frees the
> fence. The dma_fence backend performs this deallocation automatically in
> the correct manner if ops->release() is not implemented.
> 
> The backend simultaneously correctly frees struct ffs_dma_fence since
> struct dma_fence is its base class.
> 
> Remove ops->release().
> 
> Signed-off-by: Philipp Stanner <phasta@kernel.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261029125143.1744481-2-phasta@kernel.org?part=1


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] usb: gadget: f_fs: Remove deprecated dma_fence->ops
  2026-10-29 12:51 [PATCH] usb: gadget: f_fs: Remove deprecated dma_fence->ops Philipp Stanner
  2026-10-29 13:02 ` sashiko-bot
@ 2026-10-29 13:19 ` Paul Cercueil
  1 sibling, 0 replies; 3+ messages in thread
From: Paul Cercueil @ 2026-10-29 13:19 UTC (permalink / raw)
  To: Philipp Stanner, Neill Kapron, Greg Kroah-Hartman, Sumit Semwal,
	Christian König, Al Viro, Nuno Sá, Sam Day,
	Michael Bommarito, Gabriel Prostitis
  Cc: linux-usb, linux-kernel, linux-media, dri-devel

Hi Philipp,

Le jeudi 29 octobre 2026 à 13:51 +0100, Philipp Stanner a écrit :
> The dma_fence_ops function ops->release() has been deprecated because it
> prevents drivers from unloading. f_fs's implementation merely frees the
> fence. The dma_fence backend performs this deallocation automatically in
> the correct manner if ops->release() is not implemented.
> 
> The backend simultaneously correctly frees struct ffs_dma_fence since
> struct dma_fence is its base class.

For context, this .release() callback was added to avoid the implicit free of
the base class, which IIRC was a request I got during the review process of this
change set.

I'm personally fine with the change, but do we need a "keep this field at the
top" comment for the base class in the ffs_dma_fence struct? Or what's the
policy here?

Cheers,
-Paul

> 
> Remove ops->release().
> 
> Signed-off-by: Philipp Stanner <phasta@kernel.org>
> ---
>  drivers/usb/gadget/function/f_fs.c | 9 ---------
>  1 file changed, 9 deletions(-)
> 
> diff --git a/drivers/usb/gadget/function/f_fs.c
> b/drivers/usb/gadget/function/f_fs.c
> index c64a268e98a4..e8672b37e890 100644
> --- a/drivers/usb/gadget/function/f_fs.c
> +++ b/drivers/usb/gadget/function/f_fs.c
> @@ -1479,18 +1479,9 @@ static const char *ffs_dmabuf_get_timeline_name(struct
> dma_fence *fence)
>  	return "";
>  }
>  
> -static void ffs_dmabuf_fence_release(struct dma_fence *fence)
> -{
> -	struct ffs_dma_fence *dma_fence =
> -		container_of(fence, struct ffs_dma_fence, base);
> -
> -	kfree(dma_fence);
> -}
> -
>  static const struct dma_fence_ops ffs_dmabuf_fence_ops = {
>  	.get_driver_name	= ffs_dmabuf_get_driver_name,
>  	.get_timeline_name	= ffs_dmabuf_get_timeline_name,
> -	.release		= ffs_dmabuf_fence_release,
>  };
>  
>  static int ffs_dma_resv_lock(struct dma_buf *dmabuf, bool nonblock)

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-10-29 13:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-29 12:51 [PATCH] usb: gadget: f_fs: Remove deprecated dma_fence->ops Philipp Stanner
2026-10-29 13:02 ` sashiko-bot
2026-10-29 13:19 ` Paul Cercueil

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox