From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: [hare-scsi-devel:virtual-subsys 177/184] drivers/nvme/host/core.c:3778:44: error: too many arguments to function call, expected 2, have 3
Date: Wed, 6 Apr 2022 13:46:12 +0800 [thread overview]
Message-ID: <202204061335.Gk6dBO36-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git virtual-subsys
head: 13007630535ac7896532316b4e7d2c1fe868d2fc
commit: 35b5f4108aa1c4f0b2322682b5c6aa3a09314a53 [177/184] nvme: use subsystem as argument in nvme_alloc_ns_head()
config: x86_64-randconfig-a003 (https://download.01.org/0day-ci/archive/20220406/202204061335.Gk6dBO36-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c4a1b07d0979e7ff20d7d541af666d822d66b566)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git/commit/?id=35b5f4108aa1c4f0b2322682b5c6aa3a09314a53
git remote add hare-scsi-devel https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git
git fetch --no-tags hare-scsi-devel virtual-subsys
git checkout 35b5f4108aa1c4f0b2322682b5c6aa3a09314a53
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/nvme/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/nvme/host/core.c:3778:44: error: too many arguments to function call, expected 2, have 3
ret = nvme_mpath_alloc_disk(subsys, ctrl, head);
~~~~~~~~~~~~~~~~~~~~~ ^~~~
drivers/nvme/host/nvme.h:839:19: note: 'nvme_mpath_alloc_disk' declared here
static inline int nvme_mpath_alloc_disk(struct nvme_ctrl *ctrl,
^
1 error generated.
vim +3778 drivers/nvme/host/core.c
3754
3755 head = kzalloc(size, GFP_KERNEL);
3756 if (!head)
3757 goto out;
3758 ret = ida_alloc_min(&subsys->ns_ida, 1, GFP_KERNEL);
3759 if (ret < 0)
3760 goto out_free_head;
3761 head->instance = ret;
3762 INIT_LIST_HEAD(&head->list);
3763 ret = init_srcu_struct(&head->srcu);
3764 if (ret)
3765 goto out_ida_remove;
3766 head->subsys = subsys;
3767 head->ns_id = nsid;
3768 head->ids = *ids;
3769 kref_init(&head->ref);
3770
3771 if (head->ids.csi) {
3772 ret = nvme_get_effects_log(ctrl, head->ids.csi, &head->effects);
3773 if (ret)
3774 goto out_cleanup_srcu;
3775 } else
3776 head->effects = ctrl->effects;
3777
> 3778 ret = nvme_mpath_alloc_disk(subsys, ctrl, head);
3779 if (ret)
3780 goto out_cleanup_srcu;
3781
3782 list_add_tail(&head->entry, &subsys->nsheads);
3783
3784 kref_get(&subsys->ref);
3785
3786 return head;
3787 out_cleanup_srcu:
3788 cleanup_srcu_struct(&head->srcu);
3789 out_ida_remove:
3790 ida_free(&subsys->ns_ida, head->instance);
3791 out_free_head:
3792 kfree(head);
3793 out:
3794 if (ret > 0)
3795 ret = blk_status_to_errno(nvme_error_status(ret));
3796 return ERR_PTR(ret);
3797 }
3798
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-06 5: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=202204061335.Gk6dBO36-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@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.