From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-misc:dax-block-cleanup 18/29] fs/ext4/inode.c:3786:10: error: implicit declaration of function 'dax_zero_range'; did you mean 'iomap_zero_range'?
Date: Wed, 10 Nov 2021 12:10:18 +0800 [thread overview]
Message-ID: <202111101211.vrvGeyHe-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]
tree: git://git.infradead.org/users/hch/misc.git dax-block-cleanup
head: 66bc790a8f4d3b62adb7b002b63d48a49f20f7c4
commit: dd820fb94529c2cf0a1077aed2d828e9cdf51aa0 [18/29] fsdax: decouple zeroing from the iomap buffered I/O code
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add hch-misc git://git.infradead.org/users/hch/misc.git
git fetch --no-tags hch-misc dax-block-cleanup
git checkout dd820fb94529c2cf0a1077aed2d828e9cdf51aa0
# save the attached .config to linux build tree
make W=1 ARCH=um SUBARCH=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 >>):
fs/ext4/inode.c: In function 'ext4_block_zero_page_range':
>> fs/ext4/inode.c:3786:10: error: implicit declaration of function 'dax_zero_range'; did you mean 'iomap_zero_range'? [-Werror=implicit-function-declaration]
3786 | return dax_zero_range(inode, from, length, NULL,
| ^~~~~~~~~~~~~~
| iomap_zero_range
cc1: some warnings being treated as errors
vim +3786 fs/ext4/inode.c
3762
3763 /*
3764 * ext4_block_zero_page_range() zeros out a mapping of length 'length'
3765 * starting from file offset 'from'. The range to be zero'd must
3766 * be contained with in one block. If the specified range exceeds
3767 * the end of the block it will be shortened to end of the block
3768 * that corresponds to 'from'
3769 */
3770 static int ext4_block_zero_page_range(handle_t *handle,
3771 struct address_space *mapping, loff_t from, loff_t length)
3772 {
3773 struct inode *inode = mapping->host;
3774 unsigned offset = from & (PAGE_SIZE-1);
3775 unsigned blocksize = inode->i_sb->s_blocksize;
3776 unsigned max = blocksize - (offset & (blocksize - 1));
3777
3778 /*
3779 * correct length if it does not fall between
3780 * 'from' and the end of the block
3781 */
3782 if (length > max || length < 0)
3783 length = max;
3784
3785 if (IS_DAX(inode)) {
> 3786 return dax_zero_range(inode, from, length, NULL,
3787 &ext4_iomap_ops);
3788 }
3789 return __ext4_block_zero_page_range(handle, mapping, from, length);
3790 }
3791
---
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: 9733 bytes --]
reply other threads:[~2021-11-10 4:10 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=202111101211.vrvGeyHe-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.