From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/infiniband/core/uverbs_ioctl.c:82:16: sparse: sparse: incorrect type in return expression (different modifiers)
Date: Mon, 04 May 2026 09:02:16 +0800 [thread overview]
Message-ID: <202605040836.G7MlryMo-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6d35786de28116ecf78797a62b84e6bf3c45aa5a
commit: 1de9287ece44022bd694e669153fb7644804e10d RDMA: Add ib_copy_validate_udata_in()
date: 8 weeks ago
config: i386-randconfig-r122-20260503 (https://download.01.org/0day-ci/archive/20260504/202605040836.G7MlryMo-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260504/202605040836.G7MlryMo-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Fixes: 1de9287ece44 ("RDMA: Add ib_copy_validate_udata_in()")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605040836.G7MlryMo-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/infiniband/core/uverbs_ioctl.c:82:16: sparse: sparse: incorrect type in return expression (different modifiers) @@ expected int ( * )( ... ) @@ got int ( [noderef] *__v )( ... ) @@
drivers/infiniband/core/uverbs_ioctl.c:82:16: sparse: expected int ( * )( ... )
drivers/infiniband/core/uverbs_ioctl.c:82:16: sparse: got int ( [noderef] *__v )( ... )
drivers/infiniband/core/uverbs_ioctl.c:453:17: sparse: sparse: incorrect type in assignment (different modifiers) @@ expected int ( *handler )( ... ) @@ got int ( [noderef] *__v )( ... ) @@
drivers/infiniband/core/uverbs_ioctl.c:453:17: sparse: expected int ( *handler )( ... )
drivers/infiniband/core/uverbs_ioctl.c:453:17: sparse: got int ( [noderef] *__v )( ... )
vim +82 drivers/infiniband/core/uverbs_ioctl.c
72
73 uverbs_api_ioctl_handler_fn uverbs_get_handler_fn(struct ib_udata *udata)
74 {
75 struct uverbs_attr_bundle *bundle =
76 rdma_udata_to_uverbs_attr_bundle(udata);
77 struct bundle_priv *pbundle =
78 container_of(&bundle->hdr, struct bundle_priv, bundle);
79
80 lockdep_assert_held(&bundle->ufile->device->disassociate_srcu);
81
> 82 return srcu_dereference(pbundle->method_elm->handler,
83 &bundle->ufile->device->disassociate_srcu);
84 }
85
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-04 1:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202605040836.G7MlryMo-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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