From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: drivers/infiniband/core/cm.c:297:2: warning: There is an unknown macro here somewhere. Configuration is required. If rdma_for_each_port is a macro then please configure it. [unknownMacro]
Date: Mon, 04 Apr 2022 15:06:42 +0800 [thread overview]
Message-ID: <202204041559.bPAvLAhG-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3306 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
CC: linux-kernel(a)vger.kernel.org
TO: Mark Zhang <markzhang@nvidia.com>
CC: Jason Gunthorpe <jgg@ziepe.ca>
CC: Leon Romanovsky <leonro@nvidia.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3123109284176b1532874591f7c81f3837bbdc17
commit: 76039ac9095f5ee5ec7fb95ccb6a5460d5f8c3a2 IB/cm: Protect cm_dev, cm_ports and mad_agent with kref and lock
date: 10 months ago
:::::: branch date: 10 hours ago
:::::: commit date: 10 months ago
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
>> drivers/infiniband/core/cma_configfs.c:146:15: warning: syntax error [syntaxError]
CONFIGFS_ATTR(, default_roce_mode);
^
--
In file included from drivers/infiniband/core/sa_query.c:
>> drivers/infiniband/core/sa_query.c:902:16: warning: Uninitialized variables: wait_query.callback, wait_query.release, wait_query.client, wait_query.port, wait_query.mad_buf, wait_query.sm_ah, wait_query.id, wait_query.flags, wait_query.list, wait_query.seq, wait_query.timeout, wait_query.path_use [uninitvar]
if (query == wait_query) {
^
>> drivers/infiniband/core/sa_query.c:1107:32: warning: Uninitialized variable: query->seq [uninitvar]
if (nlh->nlmsg_seq == query->seq) {
^
drivers/infiniband/core/sa_query.c:1097:41: note: Assuming condition is false
if ((nlh->nlmsg_flags & NLM_F_REQUEST) ||
^
drivers/infiniband/core/sa_query.c:1107:32: note: Uninitialized variable: query->seq
if (nlh->nlmsg_seq == query->seq) {
^
--
>> drivers/infiniband/core/device.c:1016:2: warning: There is an unknown macro here somewhere. Configuration is required. If xa_for_each is a macro then please configure it. [unknownMacro]
xa_for_each (&device->compat_devs, index, cdev)
^
--
>> drivers/infiniband/core/cm.c:297:2: warning: There is an unknown macro here somewhere. Configuration is required. If rdma_for_each_port is a macro then please configure it. [unknownMacro]
rdma_for_each_port(cm_dev->ib_device, i)
^
vim +297 drivers/infiniband/core/cm.c
a977049dacdef6a Hal Rosenstock 2005-07-27 291
76039ac9095f5ee Mark Zhang 2021-06-02 292 static void cm_dev_release(struct kref *kref)
76039ac9095f5ee Mark Zhang 2021-06-02 293 {
76039ac9095f5ee Mark Zhang 2021-06-02 294 struct cm_device *cm_dev = container_of(kref, struct cm_device, kref);
76039ac9095f5ee Mark Zhang 2021-06-02 295 u32 i;
76039ac9095f5ee Mark Zhang 2021-06-02 296
76039ac9095f5ee Mark Zhang 2021-06-02 @297 rdma_for_each_port(cm_dev->ib_device, i)
76039ac9095f5ee Mark Zhang 2021-06-02 298 kfree(cm_dev->port[i - 1]);
76039ac9095f5ee Mark Zhang 2021-06-02 299
76039ac9095f5ee Mark Zhang 2021-06-02 300 kfree(cm_dev);
76039ac9095f5ee Mark Zhang 2021-06-02 301 }
76039ac9095f5ee Mark Zhang 2021-06-02 302
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-04-04 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 7:06 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-05 21:15 drivers/infiniband/core/cm.c:297:2: warning: There is an unknown macro here somewhere. Configuration is required. If rdma_for_each_port is a macro then please configure it. [unknownMacro] kernel test robot
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=202204041559.bPAvLAhG-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.org \
/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.