From: kernel test robot <lkp@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: kbuild-all@lists.01.org, linux-nvdimm@lists.01.org
Subject: [linux-nvdimm:libnvdimm-fixes 1/2] drivers/md/dm-table.c:866: undefined reference to `dax_read_lock'
Date: Fri, 18 Sep 2020 22:34:34 +0800 [thread overview]
Message-ID: <202009182231.w59t9JsH%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git libnvdimm-fixes
head: 3305ce9e90c8f1fefdf75acfbb814574c12bfcc5
commit: ec5f196ad972cd740bcbe6ef9c89a8a92d54ba44 [1/2] dm: Call proper helper to determine dax support
config: openrisc-randconfig-r022-20200918 (attached as .config)
compiler: or1k-linux-gcc (GCC) 9.3.0
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
git checkout ec5f196ad972cd740bcbe6ef9c89a8a92d54ba44
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=openrisc
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 >>):
or1k-linux-ld: drivers/md/dm-table.o: in function `device_supports_dax':
>> drivers/md/dm-table.c:866: undefined reference to `dax_read_lock'
drivers/md/dm-table.c:866:(.text+0x84c): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `dax_read_lock'
>> or1k-linux-ld: drivers/md/dm-table.c:868: undefined reference to `dax_read_unlock'
drivers/md/dm-table.c:868:(.text+0x854): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `dax_read_unlock'
# https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/commit/?id=ec5f196ad972cd740bcbe6ef9c89a8a92d54ba44
git remote add linux-nvdimm https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git
git fetch --no-tags linux-nvdimm libnvdimm-fixes
git checkout ec5f196ad972cd740bcbe6ef9c89a8a92d54ba44
vim +866 drivers/md/dm-table.c
858
859 /* validate the dax capability of the target device span */
860 int device_supports_dax(struct dm_target *ti, struct dm_dev *dev,
861 sector_t start, sector_t len, void *data)
862 {
863 int blocksize = *(int *) data, id;
864 bool rc;
865
> 866 id = dax_read_lock();
867 rc = dax_supported(dev->dax_dev, dev->bdev, blocksize, start, len);
> 868 dax_read_unlock(id);
869
870 return rc;
871 }
872
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
reply other threads:[~2020-09-18 14:35 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=202009182231.w59t9JsH%lkp@intel.com \
--to=lkp@intel.com \
--cc=jack@suse.cz \
--cc=kbuild-all@lists.01.org \
--cc=linux-nvdimm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox