summaryrefslogtreecommitdiff
path: root/kernel/resource_kunit.c
diff options
context:
space:
mode:
authorJason Gunthorpe <jgg@nvidia.com>2026-05-26 13:15:06 -0300
committerJason Gunthorpe <jgg@nvidia.com>2026-06-03 15:12:43 -0300
commitbad4e98893afdfe0b1a03433d3af53972bafc67c (patch)
tree490a8d35f4b42f27715283e36bab00397faedfaf /kernel/resource_kunit.c
parent43b57d73ebbe5e7964a8b3ee3ffde0948fae6e2e (diff)
downloadlwn-bad4e98893afdfe0b1a03433d3af53972bafc67c.tar.gz
lwn-bad4e98893afdfe0b1a03433d3af53972bafc67c.zip
RDMA: Update the query_device() op
This op hasn't followed the normal pattern of passing NULL for udata when invoked by the kernel. Instead the kernel caller creates a dummy ib_udata on the stack and passes that in. It does not seem to currently be a bug, but this flow should be modernized to use the new API flow and in the process accept NULL as well. Only mlx4 uses an input request structure, have every other driver call ib_is_udata_in_empty() to enforce the lack of request structs. Use ib_respond_empty_udata() in every driver that does not use a response struct. Ensure a check for NULL udata before calling ib_respond_udata() in bnxt_re, efa, and mlx5. Make mlx4 safe to be called with NULL. Link: https://patch.msgid.link/r/2-v1-922fa8e828ba+f7-ib_udata_stack_jgg@nvidia.com Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'kernel/resource_kunit.c')
0 files changed, 0 insertions, 0 deletions