From: Jason Gunthorpe <jgg@nvidia.com>
To: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Cc: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org,
Selvin Xavier <selvin.xavier@broadcom.com>,
patches@lists.linux.dev
Subject: Re: [PATCH v3 13/13] RDMA: Add IB_UVERBS_CORE_SUPPORT_ROBUST_UDATA
Date: Wed, 4 Mar 2026 10:11:49 -0400 [thread overview]
Message-ID: <20260304141149.GO972761@nvidia.com> (raw)
In-Reply-To: <CAHHeUGW5aOHbhETW624fM_MSkXAqUgw=T+6skPaA=R3py+9EQQ@mail.gmail.com>
On Wed, Mar 04, 2026 at 12:05:11PM +0530, Sriharsha Basavapatna wrote:
> On Wed, Mar 4, 2026 at 1:20 AM Jason Gunthorpe <jgg@nvidia.com> wrote:
> >
> > This flag can be set by drivers once they have finished auditing and
> > implementing the full udata support on every udata operation.
> >
> > My intention going forward is that driver authors proposing new udata uAPI
> > for their drivers must first do the work and set this flag.
> >
> > If this flag is not set the userspace should not try to use udata based
> > uAPI newer than this commit, though on a case by case basis it may be OK
> > based on what checks historical kernels performed on the specific call.
> >
> > Since bnxt_re is audited now, it is the first driver to set the flag.
> >
> > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> > ---
> > drivers/infiniband/core/device.c | 1 +
> > drivers/infiniband/core/uverbs_std_types_device.c | 8 ++++++++
> > drivers/infiniband/hw/bnxt_re/main.c | 1 +
> > include/rdma/ib_verbs.h | 6 ++++++
> > include/uapi/rdma/ib_user_ioctl_verbs.h | 1 +
> > 5 files changed, 17 insertions(+)
> >
> > diff --git a/drivers/infiniband/core/device.c b/drivers/infiniband/core/device.c
> > index 558b73940d6681..5b4fb47cbaeee6 100644
> > --- a/drivers/infiniband/core/device.c
> > +++ b/drivers/infiniband/core/device.c
> > @@ -2706,6 +2706,7 @@ void ib_set_device_ops(struct ib_device *dev, const struct ib_device_ops *ops)
> >
> > dev_ops->uverbs_no_driver_id_binding |=
> > ops->uverbs_no_driver_id_binding;
> > + dev_ops->uverbs_robust_udata |= dev_ops->uverbs_robust_udata;
> this should be: dev_ops->uverbs_robust_udata |= ops->uverbs_robust_udata;
Oops, are you OK otherwise?
Thanks,
Jason
next prev parent reply other threads:[~2026-03-04 14:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 19:49 [PATCH v3 00/13] Provide udata helpers and use them in bnxt_re Jason Gunthorpe
2026-03-03 19:49 ` [PATCH v3 01/13] RDMA: Use copy_struct_from_user() instead of open coding Jason Gunthorpe
2026-03-03 19:49 ` [PATCH v3 02/13] RDMA/core: Add rdma_udata_to_dev() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 03/13] RDMA: Add ib_copy_validate_udata_in() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 04/13] RDMA: Add ib_copy_validate_udata_in_cm() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 05/13] RDMA: Add ib_respond_udata() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 06/13] RDMA: Add ib_is_udata_in_empty() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 07/13] RDMA: Provide documentation about the uABI compatibility rules Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 08/13] RDMA/bnxt_re: Add compatibility checks to the uapi path Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 09/13] RDMA/bnxt_re: Add compatibility checks to the uapi path for no data Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 10/13] RDMA/bnxt_re: Add missing comp_mask validation Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 11/13] RDMA/bnxt_re: Use ib_respond_udata() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 12/13] RDMA/bnxt_re: Use ib_respond_empty_udata() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 13/13] RDMA: Add IB_UVERBS_CORE_SUPPORT_ROBUST_UDATA Jason Gunthorpe
2026-03-04 6:35 ` Sriharsha Basavapatna
2026-03-04 14:11 ` Jason Gunthorpe [this message]
2026-03-04 14:52 ` Sriharsha Basavapatna
2026-03-06 0:47 ` [PATCH v3 00/13] Provide udata helpers and use them in bnxt_re Jason Gunthorpe
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=20260304141149.GO972761@nvidia.com \
--to=jgg@nvidia.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=selvin.xavier@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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