From: kernel test robot <lkp@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [bvanassche:thread-safety 85/133] drivers/infiniband/core/uverbs_std_types_dmabuf.c:194:1: warning: unused label 'unlock'
Date: Mon, 26 Oct 2026 14:32:01 +0100 [thread overview]
Message-ID: <202610261401.SEKydNvW-lkp@intel.com> (raw)
tree: https://github.com/bvanassche/linux thread-safety
head: 09aab91c2fcb166bfe35c0f9c2c5b6b960722087
commit: ed41e5171bfb2fbf79e518ef59bfebe2446d37a7 [85/133] RDMA/core: Check the dma_resv_lock() return value
config: x86_64-randconfig-2102-20261026 (https://download.01.org/0day-ci/archive/20261026/202610261401.SEKydNvW-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261026/202610261401.SEKydNvW-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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610261401.SEKydNvW-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/infiniband/core/uverbs_std_types_dmabuf.c:194:1: warning: unused label 'unlock' [-Wunused-label]
194 | unlock:
| ^~~~~~~
1 warning generated.
vim +/unlock +194 drivers/infiniband/core/uverbs_std_types_dmabuf.c
172
173 DECLARE_UVERBS_NAMED_METHOD(
174 UVERBS_METHOD_DMABUF_ALLOC,
175 UVERBS_ATTR_FD(UVERBS_ATTR_ALLOC_DMABUF_HANDLE,
176 UVERBS_OBJECT_DMABUF,
177 UVERBS_ACCESS_NEW,
178 UA_MANDATORY),
179 UVERBS_ATTR_PTR_IN(UVERBS_ATTR_ALLOC_DMABUF_PGOFF,
180 UVERBS_ATTR_TYPE(u64),
181 UA_MANDATORY));
182
183 static void uverbs_dmabuf_fd_destroy_uobj(struct ib_uobject *uobj,
184 enum rdma_remove_reason why)
185 {
186 struct ib_uverbs_dmabuf_file *uverbs_dmabuf =
187 container_of(uobj, struct ib_uverbs_dmabuf_file, uobj);
188
189 mutex_lock(&uverbs_dmabuf->mmap_entry->dmabufs_lock);
190 if (!uverbs_dmabuf->revoked) {
191 list_del(&uverbs_dmabuf->dmabufs_elm);
192 ib_uverbs_dmabuf_revoke(uverbs_dmabuf);
193 }
> 194 unlock:
195 mutex_unlock(&uverbs_dmabuf->mmap_entry->dmabufs_lock);
196
197 /* Matches the get done as part of pgoff_to_mmap_entry() */
198 rdma_user_mmap_entry_put(uverbs_dmabuf->mmap_entry);
199 }
200
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-26 13:33 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=202610261401.SEKydNvW-lkp@intel.com \
--to=lkp@intel.com \
--cc=bvanassche@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.