From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH for-rc v2 5/6] IB/mlx4: Add support for REJ due to timeout
Date: Tue, 04 Aug 2020 19:41:18 +0800 [thread overview]
Message-ID: <202008041909.npQLUTar%lkp@intel.com> (raw)
In-Reply-To: <20200803061941.1139994-6-haakon.bugge@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]
Hi "Håkon,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on rdma/for-next]
[also build test WARNING on v5.8 next-20200803]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/H-kon-Bugge/Add-CM-packets-missing-and-harden-the-proxying/20200803-142244
base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: x86_64-randconfig-s021-20200804 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-117-g8c7aee71-dirty
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/infiniband/hw/mlx4/cm.c:496:48: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct rej_tmout_entry *item @@ got void [noderef] __rcu * @@
>> drivers/infiniband/hw/mlx4/cm.c:496:48: sparse: expected struct rej_tmout_entry *item
drivers/infiniband/hw/mlx4/cm.c:496:48: sparse: got void [noderef] __rcu *
vim +496 drivers/infiniband/hw/mlx4/cm.c
486
487 static void rej_tmout_tree_cleanup(struct mlx4_ib_sriov *sriov, int slave)
488 {
489 struct radix_tree_iter iter;
490 bool flush_needed = false;
491 __rcu void **slot;
492 int cnt = 0;
493
494 mutex_lock(&sriov->rej_tmout_lock);
495 radix_tree_for_each_slot(slot, &sriov->rej_tmout_root, &iter, 0) {
> 496 struct rej_tmout_entry *item = *slot;
497
498 if (slave < 0 || slave == item->slave) {
499 mod_delayed_work(system_wq, &item->timeout, 0);
500 flush_needed = true;
501 ++cnt;
502 }
503 }
504 mutex_unlock(&sriov->rej_tmout_lock);
505
506 if (flush_needed) {
507 flush_scheduled_work();
508 pr_debug("Deleted %d entries in radix_tree for slave %d during cleanup\n",
509 slave, cnt);
510 }
511 }
512
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38108 bytes --]
next prev parent reply other threads:[~2020-08-04 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:19 [PATCH for-rc v2 0/6] Add CM packets missing and harden the proxying Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 1/6] IB/mlx4: Add and improve logging Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 2/6] IB/mlx4: Add support for MRA Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 3/6] IB/mlx4: Separate tunnel and wire bufs parameters Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 4/6] IB/mlx4: Fix starvation in paravirt mux/demux Håkon Bugge
2020-08-03 6:19 ` [PATCH for-rc v2 5/6] IB/mlx4: Add support for REJ due to timeout Håkon Bugge
2020-08-04 11:41 ` kernel test robot [this message]
2020-08-03 6:19 ` [PATCH for-rc v2 6/6] IB/mlx4: Adjust delayed work when a dup is observed Håkon Bugge
2020-08-10 11:20 ` [PATCH for-rc v2 0/6] Add CM packets missing and harden the proxying Håkon Bugge
2020-08-10 11:46 ` Leon Romanovsky
2020-08-10 14:10 ` Gal Pressman
2020-08-10 14:23 ` Leon Romanovsky
2020-08-24 16:36 ` Jason Gunthorpe
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=202008041909.npQLUTar%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@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.