Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-rdma@vger.kernel.org, leon@kernel.org, mrgolin@amazon.com,
	 gal.pressman@linux.dev, sleybo@amazon.com, parav@nvidia.com,
	mbloch@nvidia.com,  yanjun.zhu@linux.dev,
	marco.crivellari@suse.com, roman.gushchin@linux.dev,
	 phaddad@nvidia.com, lirongqing@baidu.com, ynachum@amazon.com,
	 huangjunxian6@hisilicon.com,
	kalesh-anakkur.purayil@broadcom.com, ohartoov@nvidia.com,
	 michaelgur@nvidia.com, shayd@nvidia.com, edwards@nvidia.com,
	 sriharsha.basavapatna@broadcom.com,
	andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
	 jmoroni@google.com
Subject: Re: [PATCH rdma-next v7 03/15] RDMA/core: Introduce generic buffer descriptor infrastructure for umem
Date: Wed, 27 May 2026 19:07:57 +0200	[thread overview]
Message-ID: <ahck2d2pkw-dSNKd@FV6GYCPJ69> (raw)
In-Reply-To: <20260527155031.GA3528738@ziepe.ca>

Wed, May 27, 2026 at 05:50:31PM +0200, jgg@ziepe.ca wrote:
>On Tue, May 26, 2026 at 04:41:40PM +0200, Jiri Pirko wrote:
>
>> diff --git a/drivers/infiniband/core/uverbs_ioctl.c b/drivers/infiniband/core/uverbs_ioctl.c
>> index 6a78288e27a1..457c49d44467 100644
>> --- a/drivers/infiniband/core/uverbs_ioctl.c
>> +++ b/drivers/infiniband/core/uverbs_ioctl.c
>> @@ -597,6 +597,31 @@ void uverbs_fill_udata(struct uverbs_attr_bundle *bundle,
>>  	}
>>  }
>>  
>> +/**
>> + * uverbs_attr_get_buffer_desc - Read a buffer descriptor from a uverbs attr.
>> + * @attrs:   uverbs attribute bundle.
>> + * @attr_id: id of an UVERBS_ATTR_UMEM-typed attribute.
>> + * @desc:    descriptor to fill.
>> + *
>> + * Return: 0 on success, -ENOENT if @attr_id is not set, -EINVAL on a
>> + * malformed descriptor.
>> + */
>> +int uverbs_attr_get_buffer_desc(const struct uverbs_attr_bundle *attrs,
>> +				u16 attr_id,
>> +				struct ib_uverbs_buffer_desc *desc)
>> +{
>> +	int ret;
>> +
>> +	ret = uverbs_copy_from(desc, attrs, attr_id);
>> +	if (ret)
>> +		return ret;
>> +	if (desc->flags & ~IB_UVERBS_BUFFER_DESC_FLAGS_KNOWN_MASK)
>> +		return -EINVAL;
>> +	desc->optional_flags &= IB_UVERBS_BUFFER_DESC_OPTIONAL_FLAGS_KNOWN_MASK;
>> +	return 0;
>> +}
>> +EXPORT_SYMBOL(uverbs_attr_get_buffer_desc);
>
>This function has to go into ib_core_uverbs.c if umem is going to call
>it:
>
>ld: drivers/infiniband/core/umem.o: in function `ib_umem_get_attr':
>umem.c:(.text+0x783): undefined reference to `uverbs_attr_get_buffer_desc'
>ld: drivers/infiniband/core/umem.o: in function `ib_umem_get_attr_or_va':
>umem.c:(.text+0x82d): undefined reference to `uverbs_attr_get_buffer_desc'
>make[3]: *** [../scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1

Correct. Already fixed, sending v8.

  reply	other threads:[~2026-05-27 17:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 14:41 [PATCH rdma-next v7 00/15] RDMA: Introduce generic buffer descriptor infrastructure for umem Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 01/15] RDMA/umem: Rename ib_umem_get() to ib_umem_get_va() Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 02/15] RDMA/umem: Split ib_umem_get_va() into a thin wrapper around __ib_umem_get_va() Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 03/15] RDMA/core: Introduce generic buffer descriptor infrastructure for umem Jiri Pirko
2026-05-27 15:50   ` Jason Gunthorpe
2026-05-27 17:07     ` Jiri Pirko [this message]
2026-05-27 17:40   ` Jason Gunthorpe
2026-05-26 14:41 ` [PATCH rdma-next v7 04/15] RDMA/umem: Route ib_umem_get_va() through ib_umem_get_attr_or_va() Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 05/15] RDMA/uverbs: Push out CQ buffer umem processing into a helper Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 06/15] RDMA/uverbs: Add CQ buffer UMEM attribute and driver helpers Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 07/15] RDMA/efa: Use ib_umem_get_cq_buf() for user CQ buffer Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 08/15] RDMA/mlx5: Use ib_umem_get_cq_buf_or_va() " Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 09/15] RDMA/bnxt_re: " Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 10/15] RDMA/mlx4: Use ib_umem_get_cq_buf() " Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 11/15] RDMA/uverbs: Remove legacy umem field from struct ib_cq Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 12/15] RDMA/uverbs: Use UMEM attributes for QP creation Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 13/15] RDMA/mlx5: Use UMEM attributes for QP buffers in create_qp Jiri Pirko
2026-05-26 14:41 ` [PATCH rdma-next v7 14/15] RDMA/mlx5: Use UMEM attribute for CQ doorbell record Jiri Pirko
2026-05-27 17:41   ` Jason Gunthorpe
2026-05-26 14:41 ` [PATCH rdma-next v7 15/15] RDMA/mlx5: Use UMEM attribute for QP " Jiri Pirko

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=ahck2d2pkw-dSNKd@FV6GYCPJ69 \
    --to=jiri@resnulli.us \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=edwards@nvidia.com \
    --cc=gal.pressman@linux.dev \
    --cc=huangjunxian6@hisilicon.com \
    --cc=jgg@ziepe.ca \
    --cc=jmoroni@google.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lirongqing@baidu.com \
    --cc=marco.crivellari@suse.com \
    --cc=mbloch@nvidia.com \
    --cc=michaelgur@nvidia.com \
    --cc=mrgolin@amazon.com \
    --cc=ohartoov@nvidia.com \
    --cc=parav@nvidia.com \
    --cc=phaddad@nvidia.com \
    --cc=roman.gushchin@linux.dev \
    --cc=selvin.xavier@broadcom.com \
    --cc=shayd@nvidia.com \
    --cc=sleybo@amazon.com \
    --cc=sriharsha.basavapatna@broadcom.com \
    --cc=yanjun.zhu@linux.dev \
    --cc=ynachum@amazon.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