Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg+lists@ziepe.ca>,
	linux-rdma@vger.kernel.org, Leon Romanovsky <leon@kernel.org>
Subject: [rdma:wip/leon-for-next 33/37] drivers/infiniband/hw/mlx5/dm.c:217:16: error: 'struct mlx5_ib_dm' has no member named 'base'
Date: Tue, 17 Nov 2026 02:39:40 +0100	[thread overview]
Message-ID: <202611170202.VKw86FKB-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git wip/leon-for-next
head:   586be88310461aaded66e16c5579e384dde494b5
commit: ea97d0a83f4ed62c6f5716e27a260e21febbc79f [33/37] RDMA/mlx5: Check the DM type before mapping a MEMIC operation
config: mips-allmodconfig (https://download.01.org/0day-ci/archive/20261117/202611170202.VKw86FKB-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261117/202611170202.VKw86FKB-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/202611170202.VKw86FKB-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/infiniband/hw/mlx5/dm.c: In function 'mlx5_ib_handler_MLX5_IB_METHOD_DM_MAP_OP_ADDR':
>> drivers/infiniband/hw/mlx5/dm.c:217:16: error: 'struct mlx5_ib_dm' has no member named 'base'
     217 |         if (mdm->base.type != MLX5_IB_UAPI_DM_TYPE_MEMIC)
         |                ^~


vim +217 drivers/infiniband/hw/mlx5/dm.c

   203	
   204	static int UVERBS_HANDLER(MLX5_IB_METHOD_DM_MAP_OP_ADDR)(
   205		struct uverbs_attr_bundle *attrs)
   206	{
   207		struct ib_uobject *uobj = uverbs_attr_get_uobject(
   208			attrs, MLX5_IB_ATTR_DM_MAP_OP_ADDR_REQ_HANDLE);
   209		struct mlx5_ib_dev *dev = to_mdev(uobj->context->device);
   210		struct ib_dm *ibdm = uobj->object;
   211		struct mlx5_ib_dm *mdm = to_mdm(ibdm);
   212		struct mlx5_ib_dm_memic *dm = to_memic(ibdm);
   213		struct mlx5_ib_dm_op_entry *op_entry;
   214		int err;
   215		u8 op;
   216	
 > 217		if (mdm->base.type != MLX5_IB_UAPI_DM_TYPE_MEMIC)
   218			return -EOPNOTSUPP;
   219	
   220		err = uverbs_copy_from(&op, attrs, MLX5_IB_ATTR_DM_MAP_OP_ADDR_REQ_OP);
   221		if (err)
   222			return err;
   223	
   224		if (op >= BITS_PER_TYPE(u32))
   225			return -EOPNOTSUPP;
   226	
   227		if (!(MLX5_CAP_DEV_MEM(dev->mdev, memic_operations) & BIT(op)))
   228			return -EOPNOTSUPP;
   229	
   230		mutex_lock(&dm->ops_xa_lock);
   231		err = map_existing_op(dm, op, attrs);
   232		if (!err || err != -ENOENT)
   233			goto err_unlock;
   234	
   235		op_entry = kzalloc_obj(*op_entry);
   236		if (!op_entry) {
   237			err = -ENOMEM;
   238			goto err_unlock;
   239		}
   240	
   241		err = mlx5_cmd_alloc_memic_op(&dev->dm, dm->base.dev_addr, op,
   242					      &op_entry->op_addr);
   243		if (err) {
   244			kfree(op_entry);
   245			goto err_unlock;
   246		}
   247		op_entry->op = op;
   248		op_entry->dm = dm;
   249	
   250		err = add_dm_mmap_entry(uobj->context, &op_entry->mentry,
   251					MLX5_IB_MMAP_TYPE_MEMIC_OP, dm->base.size,
   252					op_entry->op_addr & PAGE_MASK);
   253		if (err) {
   254			mlx5_cmd_dealloc_memic_op(&dev->dm, dm->base.dev_addr, op);
   255			kfree(op_entry);
   256			goto err_unlock;
   257		}
   258		/* From this point, entry will be freed by mmap_free */
   259		kref_get(&dm->ref);
   260	
   261		err = copy_op_to_user(op_entry, attrs);
   262		if (err)
   263			goto err_remove;
   264	
   265		err = xa_insert(&dm->ops, op, op_entry, GFP_KERNEL);
   266		if (err)
   267			goto err_remove;
   268		mutex_unlock(&dm->ops_xa_lock);
   269	
   270		return 0;
   271	
   272	err_remove:
   273		rdma_user_mmap_entry_remove(&op_entry->mentry.rdma_entry);
   274	err_unlock:
   275		mutex_unlock(&dm->ops_xa_lock);
   276	
   277		return err;
   278	}
   279	

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

                 reply	other threads:[~2026-11-17  1:40 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=202611170202.VKw86FKB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dennylin0707@gmail.com \
    --cc=dledford@redhat.com \
    --cc=jgg+lists@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@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