From: Jason Gunthorpe <jgg@ziepe.ca>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/core: Remove _ib_copy_validate_udata_in() and _ib_respond_udata() stubs
Date: Tue, 19 May 2026 19:49:11 -0300 [thread overview]
Message-ID: <20260519224911.GP7702@ziepe.ca> (raw)
In-Reply-To: <20260519-rdma-core-fix-ib_udata-redef-errors-v1-1-671bf2697fa5@kernel.org>
On Tue, May 19, 2026 at 11:24:36AM -0700, Nathan Chancellor wrote:
> After commit 65b044cee9fb ("RDMA/core: Move the _ib_copy_validate_udata*
> functions to ib_core_uverbs"), builds without INFINIBAND_USER_ACCESS
> enabled fail with:
>
> drivers/infiniband/core/ib_core_uverbs.c:433:5: error: redefinition of '_ib_copy_validate_udata_in'
> 433 | int _ib_copy_validate_udata_in(struct ib_udata *udata, void *req,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from include/rdma/uverbs_std_types.h:10,
> from drivers/infiniband/core/uverbs.h:49,
> from drivers/infiniband/core/ib_core_uverbs.c:10:
> include/rdma/uverbs_ioctl.h:961:19: note: previous definition of '_ib_copy_validate_udata_in' with type 'int(struct ib_udata *, void *, size_t, size_t)' {aka 'int(struct ib_udata *, void *, long unsigned int, long unsigned int)'}
> 961 | static inline int _ib_copy_validate_udata_in(struct ib_udata *udata, void *req,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/infiniband/core/ib_core_uverbs.c:483:5: error: redefinition of '_ib_respond_udata'
> 483 | int _ib_respond_udata(struct ib_udata *udata, const void *src, size_t len)
> | ^~~~~~~~~~~~~~~~~
> include/rdma/uverbs_ioctl.h:968:19: note: previous definition of '_ib_respond_udata' with type 'int(struct ib_udata *, const void *, size_t)' {aka 'int(struct ib_udata *, const void *, long unsigned int)'}
> 968 | static inline int _ib_respond_udata(struct ib_udata *udata, const void *src,
> | ^~~~~~~~~~~~~~~~~
>
> Remove the stubs and adjust the prototypes for _ib_respond_udata() and
> _ib_copy_validate_udata_in(), as they will always be available when
> INFINIBAND is enabled.
Ugh, we should get rid of this option these days..
The right thing is to #ifdef away the moved C code since it doesn't
get removed by the makefile and keep the static inlines.
Possibly even all of drivers/infiniband/core/ib_core_uverbs.c should
be put under a conditional, I'll look at that later
--- a/drivers/infiniband/core/ib_core_uverbs.c
+++ b/drivers/infiniband/core/ib_core_uverbs.c
@@ -417,6 +417,7 @@ struct ib_device *rdma_udata_to_dev(struct ib_udata *udata)
}
EXPORT_SYMBOL(rdma_udata_to_dev);
+#if IS_ENABLED(CONFIG_INFINIBAND_USER_ACCESS)
uverbs_api_ioctl_handler_fn uverbs_get_handler_fn(struct ib_udata *udata)
{
struct uverbs_attr_bundle *bundle =
@@ -501,3 +502,4 @@ int _ib_respond_udata(struct ib_udata *udata, const void *src, size_t len)
return -EFAULT;
}
EXPORT_SYMBOL(_ib_respond_udata);
+#endif
I guess I'll squash it in, unlucky that 0-day didn't notice this, or
maybe it isn't working anymore...
Thanks,
Jason
prev parent reply other threads:[~2026-05-19 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 18:24 [PATCH] RDMA/core: Remove _ib_copy_validate_udata_in() and _ib_respond_udata() stubs Nathan Chancellor
2026-05-19 22:49 ` Jason Gunthorpe [this message]
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=20260519224911.GP7702@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nathan@kernel.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