From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Edward Srouji" <edwards@nvidia.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org,
"Yishai Hadas" <yishaih@nvidia.com>
Subject: Re: [PATCH rdma-next 1/2] RDMA/uverbs: Add DMABUF object type and operations
Date: Wed, 21 Jan 2026 10:32:46 +0200 [thread overview]
Message-ID: <20260121083246.GV13201@unreal> (raw)
In-Reply-To: <20260120181520.GS961572@ziepe.ca>
On Tue, Jan 20, 2026 at 02:15:20PM -0400, Jason Gunthorpe wrote:
> On Thu, Jan 08, 2026 at 01:11:14PM +0200, Edward Srouji wrote:
> > void rdma_user_mmap_entry_remove(struct rdma_user_mmap_entry *entry)
> > {
> > + struct ib_uverbs_dmabuf_file *uverbs_dmabuf, *tmp;
> > +
> > if (!entry)
> > return;
> >
> > + mutex_lock(&entry->dmabufs_lock);
> > xa_lock(&entry->ucontext->mmap_xa);
> > entry->driver_removed = true;
> > xa_unlock(&entry->ucontext->mmap_xa);
> > + list_for_each_entry_safe(uverbs_dmabuf, tmp, &entry->dmabufs, dmabufs_elm) {
> > + dma_resv_lock(uverbs_dmabuf->dmabuf->resv, NULL);
> > + list_del(&uverbs_dmabuf->dmabufs_elm);
> > + uverbs_dmabuf->revoked = true;
> > + dma_buf_move_notify(uverbs_dmabuf->dmabuf);
> > + dma_resv_unlock(uverbs_dmabuf->dmabuf->resv);
>
> This will need the same wait that Christian pointed out for VFIO..
Yes, something like this is missing
https://lore.kernel.org/all/20260120-dmabuf-revoke-v3-6-b7e0b07b8214@nvidia.com/
<...>
> > +struct ib_uverbs_dmabuf_file {
> > + struct ib_uobject uobj;
> > + struct dma_buf *dmabuf;
> > + struct list_head dmabufs_elm;
> > + struct rdma_user_mmap_entry *mmap_entry;
> > + struct dma_buf_phys_vec phys_vec;
>
> Oh, are we going to have weird merge conflicts with this Leon?
No, Alex created a shared branch with the rename already applied for me.
I had planned to merge it into the RDMA tree before taking this series, and
then update dma_buf_phys_vec to phys_vec locally.
>
> > +static int uverbs_dmabuf_attach(struct dma_buf *dmabuf,
> > + struct dma_buf_attachment *attachment)
> > +{
> > + struct ib_uverbs_dmabuf_file *priv = dmabuf->priv;
> > +
> > + if (!attachment->peer2peer)
> > + return -EOPNOTSUPP;
> > +
> > + if (priv->revoked)
> > + return -ENODEV;
>
> This should only be checked in map
I disagree with word "only", the more accurate word is "too". There is
no need to allow new importer attach if this exporter is marked as
revoked.
>
> This should also eventually call the new revoke testing function Leon
> is adding
We will add it once my series will be accepted.
Thanks
>
> Jason
next prev parent reply other threads:[~2026-01-21 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 11:11 [PATCH rdma-next 0/2] RDMA: Add support for exporting dma-buf file descriptors Edward Srouji
2026-01-08 11:11 ` [PATCH rdma-next 1/2] RDMA/uverbs: Add DMABUF object type and operations Edward Srouji
2026-01-20 18:15 ` Jason Gunthorpe
2026-01-21 8:32 ` Leon Romanovsky [this message]
2026-01-21 13:56 ` Jason Gunthorpe
2026-01-21 16:27 ` Yishai Hadas
2026-01-21 10:07 ` Yishai Hadas
2026-01-25 14:31 ` Leon Romanovsky
2026-01-08 11:11 ` [PATCH rdma-next 2/2] RDMA/mlx5: Implement DMABUF export ops Edward Srouji
2026-01-20 18:18 ` Jason Gunthorpe
2026-01-21 10:35 ` Yishai Hadas
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=20260121083246.GV13201@unreal \
--to=leon@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=edwards@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=yishaih@nvidia.com \
/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