From: Simona Vetter <simona.vetter@ffwll.ch>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: simona@ffwll.ch, airlied@gmail.com, asrivats@redhat.com,
andyshrk@163.com, christian.koenig@amd.com,
boris.brezillon@collabora.com, mripard@kernel.org,
maarten.lankhorst@linux.intel.com,
dri-devel@lists.freedesktop.org,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v3] drm/gem: Internally test import_attach for imported objects
Date: Wed, 30 Apr 2025 11:07:17 +0200 [thread overview]
Message-ID: <aBHoRTdsdOLFhzfg@phenom.ffwll.local> (raw)
In-Reply-To: <Z_96e7Lv-sEDUS6U@phenom.ffwll.local>
On Wed, Apr 16, 2025 at 11:38:03AM +0200, Simona Vetter wrote:
> On Wed, Apr 16, 2025 at 08:57:45AM +0200, Thomas Zimmermann wrote:
> > Test struct drm_gem_object.import_attach to detect imported objects.
> >
> > During object clenanup, the dma_buf field might be NULL. Testing it in
> > an object's free callback then incorrectly does a cleanup as for native
> > objects. Happens for calls to drm_mode_destroy_dumb_ioctl() that
> > clears the dma_buf field in drm_gem_object_exported_dma_buf_free().
> >
> > v3:
> > - only test for import_attach (Boris)
> > v2:
> > - use import_attach.dmabuf instead of dma_buf (Christian)
> >
> > Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> > Fixes: b57aa47d39e9 ("drm/gem: Test for imported GEM buffers with helper")
> > Reported-by: Andy Yan <andyshrk@163.com>
> > Closes: https://lore.kernel.org/dri-devel/38d09d34.4354.196379aa560.Coremail.andyshrk@163.com/
> > Tested-by: Andy Yan <andyshrk@163.com>
> > Cc: Thomas Zimmermann <tzimmermann@suse.de>
> > Cc: Anusha Srivatsa <asrivats@redhat.com>
> > Cc: Christian König <christian.koenig@amd.com>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Maxime Ripard <mripard@kernel.org>
> > Cc: David Airlie <airlied@gmail.com>
> > Cc: Simona Vetter <simona@ffwll.ch>
> > Cc: Sumit Semwal <sumit.semwal@linaro.org>
> > Cc: "Christian König" <christian.koenig@amd.com>
> > Cc: dri-devel@lists.freedesktop.org
> > Cc: linux-media@vger.kernel.org
> > Cc: linaro-mm-sig@lists.linaro.org
>
> Reviewed-by: Simona Vetter <simona.vetter@ffwll.ch>
Also quick doc request: We do have a bit of overview documentation for
prime here about specifically this lifetime fun, and why there's a chain
of references and hence a distinction between imported foreign dma-buf and
re-imported native dma-buf:
https://dri.freedesktop.org/docs/drm/gpu/drm-mm.html#reference-counting-for-gem-drivers
I think it would be good to augment this with more links to functions
(like this one recently added and fixed in this patch here) and struct
members to that overview. And maybe also link from key function and struct
functions back to that overview doc. Otherwise I think the next person
will get confused by this rather tricky code again and break a corner
cases.
Thanks, Sima
>
> > ---
> > include/drm/drm_gem.h | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/include/drm/drm_gem.h b/include/drm/drm_gem.h
> > index 9b71f7a9f3f8..a3133a08267c 100644
> > --- a/include/drm/drm_gem.h
> > +++ b/include/drm/drm_gem.h
> > @@ -588,8 +588,7 @@ static inline bool drm_gem_object_is_shared_for_memory_stats(struct drm_gem_obje
> > */
> > static inline bool drm_gem_is_imported(const struct drm_gem_object *obj)
> > {
> > - /* The dma-buf's priv field points to the original GEM object. */
> > - return obj->dma_buf && (obj->dma_buf->priv != obj);
> > + return !!obj->import_attach;
> > }
> >
> > #ifdef CONFIG_LOCKDEP
> > --
> > 2.49.0
> >
>
> --
> Simona Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2025-04-30 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 6:57 [PATCH v3] drm/gem: Internally test import_attach for imported objects Thomas Zimmermann
2025-04-16 8:00 ` Boris Brezillon
2025-04-16 9:38 ` Simona Vetter
2025-04-30 9:07 ` Simona Vetter [this message]
2025-05-05 7:29 ` Boris Brezillon
2025-05-06 7:39 ` Thomas Zimmermann
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=aBHoRTdsdOLFhzfg@phenom.ffwll.local \
--to=simona.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=andyshrk@163.com \
--cc=asrivats@redhat.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--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