public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yishai Hadas <yishaih@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Leon Romanovsky <leon@kernel.org>,
	Edward Srouji <edwards@nvidia.com>
Subject: drivers/infiniband/core/ib_core_uverbs.c:249:undefined reference to `dma_buf_move_notify'
Date: Thu, 19 Feb 2026 08:45:30 +0800	[thread overview]
Message-ID: <202602190832.RTYwo5mP-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   23b0f90ba871f096474e1c27c3d14f455189d2d9
commit: 0ac6f4056c4a257f4b230b910e3e6fee6c6fc9b9 RDMA/uverbs: Add DMABUF object type and operations
date:   10 days ago
config: x86_64-randconfig-005-20250616 (https://download.01.org/0day-ci/archive/20260219/202602190832.RTYwo5mP-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260219/202602190832.RTYwo5mP-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/202602190832.RTYwo5mP-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: drivers/infiniband/core/ib_core_uverbs.o: in function `rdma_user_mmap_entry_remove':
>> drivers/infiniband/core/ib_core_uverbs.c:249:(.text+0x8bd): undefined reference to `dma_buf_move_notify'
>> ld: drivers/infiniband/core/ib_core_uverbs.c:250:(.text+0x8de): undefined reference to `dma_resv_wait_timeout'
   ld: drivers/infiniband/core/ib_core_uverbs.o: in function `dma_resv_unlock':
>> include/linux/dma-resv.h:463:(.text+0x8f1): undefined reference to `dma_resv_reset_max_fences'


vim +249 drivers/infiniband/core/ib_core_uverbs.c

   223	
   224	/**
   225	 * rdma_user_mmap_entry_remove() - Drop reference to entry and
   226	 *				   mark it as unmmapable
   227	 *
   228	 * @entry: the entry to insert into the mmap_xa
   229	 *
   230	 * Drivers can call this to prevent userspace from creating more mappings for
   231	 * entry, however existing mmaps continue to exist and ops->mmap_free() will
   232	 * not be called until all user mmaps are destroyed.
   233	 */
   234	void rdma_user_mmap_entry_remove(struct rdma_user_mmap_entry *entry)
   235	{
   236		struct ib_uverbs_dmabuf_file *uverbs_dmabuf, *tmp;
   237	
   238		if (!entry)
   239			return;
   240	
   241		mutex_lock(&entry->dmabufs_lock);
   242		xa_lock(&entry->ucontext->mmap_xa);
   243		entry->driver_removed = true;
   244		xa_unlock(&entry->ucontext->mmap_xa);
   245		list_for_each_entry_safe(uverbs_dmabuf, tmp, &entry->dmabufs, dmabufs_elm) {
   246			dma_resv_lock(uverbs_dmabuf->dmabuf->resv, NULL);
   247			list_del(&uverbs_dmabuf->dmabufs_elm);
   248			uverbs_dmabuf->revoked = true;
 > 249			dma_buf_move_notify(uverbs_dmabuf->dmabuf);
 > 250			dma_resv_wait_timeout(uverbs_dmabuf->dmabuf->resv,
   251					      DMA_RESV_USAGE_BOOKKEEP, false,
   252					      MAX_SCHEDULE_TIMEOUT);
   253			dma_resv_unlock(uverbs_dmabuf->dmabuf->resv);
   254			kref_put(&uverbs_dmabuf->kref, ib_uverbs_dmabuf_done);
   255			wait_for_completion(&uverbs_dmabuf->comp);
   256		}
   257		mutex_unlock(&entry->dmabufs_lock);
   258	
   259		kref_put(&entry->ref, rdma_user_mmap_entry_free);
   260	}
   261	EXPORT_SYMBOL(rdma_user_mmap_entry_remove);
   262	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-02-19  0:46 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=202602190832.RTYwo5mP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=edwards@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yishaih@nvidia.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