From: kernel test robot <lkp@intel.com>
To: Parav Pandit <parav@nvidia.com>, "hch@lst.de" <hch@lst.de>
Cc: kbuild-all@lists.01.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
syzbot <syzbot+34dc2fea3478e659af01@syzkaller.appspotmail.com>,
"linaro-mm-sig-owner@lists.linaro.org"
<linaro-mm-sig-owner@lists.linaro.org>,
Jakub Kicinski <kuba@kernel.org>,
"christian.koenig@amd.com" <christian.koenig@amd.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH] RDMA: Fix software RDMA drivers for dma mapping error
Date: Wed, 28 Oct 2020 16:03:39 +0800 [thread overview]
Message-ID: <202010281512.8DnwQghg-lkp@intel.com> (raw)
In-Reply-To: <BY5PR12MB43221380BB0259FF0693BB0CDC160@BY5PR12MB4322.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3355 bytes --]
Hi Parav,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on rdma/for-next]
[also build test ERROR on v5.10-rc1 next-20201028]
[cannot apply to hch-configfs/for-next]
[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/Parav-Pandit/RDMA-Fix-software-RDMA-drivers-for-dma-mapping-error/20201027-205440
base: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
config: x86_64-rhel-8.3 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/cbe9509f0d3a076646d576c1d1f5adc59159316c
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Parav-Pandit/RDMA-Fix-software-RDMA-drivers-for-dma-mapping-error/20201027-205440
git checkout cbe9509f0d3a076646d576c1d1f5adc59159316c
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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/infiniband/sw/rxe/rxe_verbs.c: In function 'rxe_register_device':
>> drivers/infiniband/sw/rxe/rxe_verbs.c:1133:48: error: 'DMA_MASK_NONE' undeclared (first use in this function); did you mean 'CPU_MASK_NONE'?
1133 | err = dma_coerce_mask_and_coherent(&dev->dev, DMA_MASK_NONE);
| ^~~~~~~~~~~~~
| CPU_MASK_NONE
drivers/infiniband/sw/rxe/rxe_verbs.c:1133:48: note: each undeclared identifier is reported only once for each function it appears in
--
drivers/infiniband/sw/siw/siw_main.c: In function 'siw_device_create':
>> drivers/infiniband/sw/siw/siw_main.c:387:51: error: 'DMA_MASK_NONE' undeclared (first use in this function); did you mean 'CPU_MASK_NONE'?
387 | if (dma_coerce_mask_and_coherent(&base_dev->dev, DMA_MASK_NONE))
| ^~~~~~~~~~~~~
| CPU_MASK_NONE
drivers/infiniband/sw/siw/siw_main.c:387:51: note: each undeclared identifier is reported only once for each function it appears in
vim +1133 drivers/infiniband/sw/rxe/rxe_verbs.c
1115
1116 int rxe_register_device(struct rxe_dev *rxe, const char *ibdev_name)
1117 {
1118 int err;
1119 struct ib_device *dev = &rxe->ib_dev;
1120 struct crypto_shash *tfm;
1121
1122 strlcpy(dev->node_desc, "rxe", sizeof(dev->node_desc));
1123
1124 dev->node_type = RDMA_NODE_IB_CA;
1125 dev->phys_port_cnt = 1;
1126 dev->num_comp_vectors = num_possible_cpus();
1127 dev->dev.parent = rxe_dma_device(rxe);
1128 dev->local_dma_lkey = 0;
1129 addrconf_addr_eui48((unsigned char *)&dev->node_guid,
1130 rxe->ndev->dev_addr);
1131 dev->dev.dma_parms = &rxe->dma_parms;
1132 dma_set_max_seg_size(&dev->dev, UINT_MAX);
> 1133 err = dma_coerce_mask_and_coherent(&dev->dev, DMA_MASK_NONE);
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41020 bytes --]
[-- Attachment #3: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-10-28 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 19:03 WARNING in dma_map_page_attrs syzbot
2020-10-22 13:41 ` Christoph Hellwig
2020-10-24 3:07 ` syzbot
2020-10-24 18:15 ` Jakub Kicinski
2020-10-26 5:23 ` Parav Pandit
2020-10-27 8:11 ` hch
2020-10-27 12:52 ` Parav Pandit
2020-10-28 8:03 ` kernel test robot [this message]
2020-10-28 17:31 ` hch
2020-10-30 9:35 ` Parav Pandit
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=202010281512.8DnwQghg-lkp@intel.com \
--to=lkp@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linaro-mm-sig-owner@lists.linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=syzbot+34dc2fea3478e659af01@syzkaller.appspotmail.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