From: kernel test robot <lkp@intel.com>
To: Zhiqiang Liu <liuzhiqiang26@huawei.com>,
agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, linfeilong <linfeilong@huawei.com>,
lixiaokeng <lixiaokeng@huawei.com>,
"wubo (T)" <wubo40@huawei.com>
Subject: Re: [PATCH] md/dm-mpath: check whether all pgpaths have same uuid in multipath_ctr()
Date: Sat, 20 Mar 2021 22:34:39 +0800 [thread overview]
Message-ID: <202103202207.vSwVf5b2-lkp@intel.com> (raw)
In-Reply-To: <c8f86351-3036-0945-90d2-2e020d68ccf2@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
Hi Zhiqiang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on dm/for-next]
[also build test ERROR on mkp-scsi/for-next scsi/for-next v5.12-rc3 next-20210319]
[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/Zhiqiang-Liu/md-dm-mpath-check-whether-all-pgpaths-have-same-uuid-in-multipath_ctr/20210320-195717
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: i386-randconfig-c001-20210320 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/f8f908f78541c7da502df6f31f772ca6e8c71732
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Zhiqiang-Liu/md-dm-mpath-check-whether-all-pgpaths-have-same-uuid-in-multipath_ctr/20210320-195717
git checkout f8f908f78541c7da502df6f31f772ca6e8c71732
# save the attached .config to linux build tree
make W=1 ARCH=i386
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 >>, old ones prefixed by <<):
>> ERROR: modpost: "scsi_device_from_queue" [drivers/md/dm-multipath.ko] undefined!
>> ERROR: modpost: "scsi_vpd_lun_id" [drivers/md/dm-multipath.ko] undefined!
---
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: 35908 bytes --]
next prev parent reply other threads:[~2021-03-20 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 7:19 [PATCH] md/dm-mpath: check whether all pgpaths have same uuid in multipath_ctr() Zhiqiang Liu
2021-03-20 14:34 ` kernel test robot [this message]
2021-03-22 8:11 ` Christoph Hellwig
2021-03-22 14:22 ` Mike Snitzer
2021-03-23 7:47 ` lixiaokeng
2021-03-23 17:11 ` Ewan D. Milne
2021-03-25 1:12 ` Zhiqiang Liu
2021-03-25 1:21 ` Zhiqiang Liu
2021-03-25 15:14 ` Mike Snitzer
2021-03-26 17:12 ` [dm-devel] " Martin Wilck
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=202103202207.vSwVf5b2-lkp@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=lixiaokeng@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=snitzer@redhat.com \
--cc=wubo40@huawei.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;
as well as URLs for NNTP newsgroup(s).