From: Gustavo Padovan <gustavo@padovan.org>
To: Akhil P Oommen <akhilpo@codeaurora.org>,
sumit.semwal@linaro.org, jcrouse@codeaurora.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, smasetty@codeaurora.org
Subject: Re: [PATCH v2] dma-buf/fence: Take refcount on the module that owns the fence
Date: Fri, 22 Jun 2018 07:04:16 -0300 [thread overview]
Message-ID: <1529661856.7034.404.camel@padovan.org> (raw)
In-Reply-To: <1529660407-6266-1-git-send-email-akhilpo@codeaurora.org>
Hi Akhil,
On Fri, 2018-06-22 at 15:10 +0530, Akhil P Oommen wrote:
> Each fence object holds function pointers of the module that
> initialized
> it. Allowing the module to unload before this fence's release is
> catastrophic. So, keep a refcount on the module until the fence is
> released.
>
> Signed-off-by: Akhil P Oommen <akhilpo@codeaurora.org>
> ---
> Changes in v2:
> - added description for the new function parameter.
>
> drivers/dma-buf/dma-fence.c | 16 +++++++++++++---
> include/linux/dma-fence.h | 10 ++++++++--
> 2 files changed, 21 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-
> fence.c
> index 4edb9fd..2aaa44e 100644
> --- a/drivers/dma-buf/dma-fence.c
> +++ b/drivers/dma-buf/dma-fence.c
> @@ -18,6 +18,7 @@
> * more details.
> */
>
> +#include <linux/module.h>
> #include <linux/slab.h>
> #include <linux/export.h>
> #include <linux/atomic.h>
> @@ -168,6 +169,7 @@ void dma_fence_release(struct kref *kref)
> {
> struct dma_fence *fence =
> container_of(kref, struct dma_fence, refcount);
> + struct module *module = fence->owner;
>
> trace_dma_fence_destroy(fence);
>
> @@ -178,6 +180,8 @@ void dma_fence_release(struct kref *kref)
> fence->ops->release(fence);
> else
> dma_fence_free(fence);
> +
> + module_put(module);
> }
> EXPORT_SYMBOL(dma_fence_release);
>
> @@ -541,6 +545,7 @@ struct default_wait_cb {
>
> /**
> * dma_fence_init - Initialize a custom fence.
> + * @module: [in] the module that calls this API
> * @fence: [in] the fence to initialize
> * @ops: [in] the dma_fence_ops for operations on this
> fence
> * @lock: [in] the irqsafe spinlock to use for locking
> this fence
> @@ -556,8 +561,9 @@ struct default_wait_cb {
> * to check which fence is later by simply using dma_fence_later.
> */
> void
> -dma_fence_init(struct dma_fence *fence, const struct dma_fence_ops
> *ops,
> - spinlock_t *lock, u64 context, unsigned seqno)
> +_dma_fence_init(struct module *module, struct dma_fence *fence,
> + const struct dma_fence_ops *ops, spinlock_t *lock,
> + u64 context, unsigned seqno)
> {
> BUG_ON(!lock);
> BUG_ON(!ops || !ops->wait || !ops->enable_signaling ||
> @@ -571,7 +577,11 @@ struct default_wait_cb {
> fence->seqno = seqno;
> fence->flags = 0UL;
> fence->error = 0;
> + fence->owner = module;
> +
> + if (!try_module_get(module))
> + fence->owner = NULL;
>
> trace_dma_fence_init(fence);
> }
> -EXPORT_SYMBOL(dma_fence_init);
> +EXPORT_SYMBOL(_dma_fence_init);
Do we still need to export the symbol, it won't be called from outside
anymore? Other than that looks good to me:
Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.com>
Gustavo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-22 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 9:40 [PATCH v2] dma-buf/fence: Take refcount on the module that owns the fence Akhil P Oommen
2018-06-22 10:04 ` Gustavo Padovan [this message]
2018-06-22 10:08 ` Chris Wilson
2018-06-22 11:42 ` Akhil P Oommen
2018-06-25 7:50 ` Daniel Vetter
2018-06-25 15:51 ` Akhil P Oommen
2018-06-26 8:17 ` Daniel Vetter
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=1529661856.7034.404.camel@padovan.org \
--to=gustavo@padovan.org \
--cc=akhilpo@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jcrouse@codeaurora.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=smasetty@codeaurora.org \
--cc=sumit.semwal@linaro.org \
/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