From: kernel test robot <lkp@intel.com>
To: Zhang Yi <yi.zhang@huaweicloud.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, djwong@kernel.org, hch@infradead.org,
brauner@kernel.org, david@fromorbit.com, chandanbabu@kernel.org,
jack@suse.cz, yi.zhang@huawei.com, yi.zhang@huaweicloud.com,
chengzhihao1@huawei.com, yukuai3@huawei.com
Subject: Re: [PATCH v2 1/3] iomap: pass blocksize to iomap_truncate_page()
Date: Fri, 17 May 2024 07:03:46 +0800 [thread overview]
Message-ID: <202405170624.liC4qYj3-lkp@intel.com> (raw)
In-Reply-To: <20240516073001.1066373-2-yi.zhang@huaweicloud.com>
Hi Zhang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on linus/master v6.9 next-20240516]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Zhang-Yi/iomap-pass-blocksize-to-iomap_truncate_page/20240516-154238
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20240516073001.1066373-2-yi.zhang%40huaweicloud.com
patch subject: [PATCH v2 1/3] iomap: pass blocksize to iomap_truncate_page()
config: arm-randconfig-r111-20240517 (https://download.01.org/0day-ci/archive/20240517/202405170624.liC4qYj3-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240517/202405170624.liC4qYj3-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405170624.liC4qYj3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/iomap/buffered-io.c:1453:28: sparse: sparse: incompatible types in comparison expression (different signedness):
fs/iomap/buffered-io.c:1453:28: sparse: long long *
fs/iomap/buffered-io.c:1453:28: sparse: unsigned long long [usertype] *
vim +1453 fs/iomap/buffered-io.c
1446
1447 int
1448 iomap_truncate_page(struct inode *inode, loff_t pos, unsigned int blocksize,
1449 bool *did_zero, const struct iomap_ops *ops)
1450 {
1451 loff_t start = pos;
1452 unsigned int off = is_power_of_2(blocksize) ? (pos & (blocksize - 1)) :
> 1453 do_div(pos, blocksize);
1454
1455 /* Block boundary? Nothing to do */
1456 if (!off)
1457 return 0;
1458 return iomap_zero_range(inode, start, blocksize - off, did_zero, ops);
1459 }
1460 EXPORT_SYMBOL_GPL(iomap_truncate_page);
1461
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-16 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 7:29 [PATCH v2 0/3] iomap/xfs: fix stale data exposure when truncating realtime inodes Zhang Yi
2024-05-16 7:29 ` [PATCH v2 1/3] iomap: pass blocksize to iomap_truncate_page() Zhang Yi
2024-05-16 19:31 ` kernel test robot
2024-05-16 23:03 ` kernel test robot [this message]
2024-05-16 7:30 ` [PATCH v2 2/3] fsdax: pass blocksize to dax_truncate_page() Zhang Yi
2024-05-16 7:30 ` [PATCH v2 3/3] xfs: correct the zeroing truncate range Zhang Yi
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=202405170624.liC4qYj3-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=yukuai3@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).