From: kernel test robot <lkp@intel.com>
To: Zhang Yi <yi.zhang@huaweicloud.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC 13/18] ext4: impliment writeback iomap path
Date: Fri, 24 Nov 2023 23:41:59 +0800 [thread overview]
Message-ID: <202311241945.TOPPNdHa-lkp@intel.com> (raw)
In-Reply-To: <20231123125121.4064694-14-yi.zhang@huaweicloud.com>
Hi Zhang,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.6]
[cannot apply to tytso-ext4/dev linus/master v6.7-rc2 v6.7-rc1 next-20231124]
[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/ext4-make-ext4_es_lookup_extent-return-the-next-extent-if-not-found/20231124-005707
base: v6.6
patch link: https://lore.kernel.org/r/20231123125121.4064694-14-yi.zhang%40huaweicloud.com
patch subject: [PATCH RFC 13/18] ext4: impliment writeback iomap path
config: m68k-sun3x_defconfig (https://download.01.org/0day-ci/archive/20231124/202311241945.TOPPNdHa-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231124/202311241945.TOPPNdHa-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/202311241945.TOPPNdHa-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/ext4/ext4_jbd2.h:17,
from fs/ext4/inode.c:45:
fs/ext4/inode.c: In function 'ext4_iomap_prepare_ioend':
>> fs/ext4/inode.c:3913:26: warning: format '%ld' expects argument of type 'long int', but argument 5 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
3913 | "%s: jbd2_start: %ld blocks, ino %lu; err %d\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3914 | __func__, ioend->io_size >> inode->i_blkbits,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| size_t {aka unsigned int}
fs/ext4/ext4.h:3162:31: note: in definition of macro 'ext4_msg'
3162 | __ext4_msg(sb, level, fmt, ##__VA_ARGS__)
| ^~~
fs/ext4/inode.c:3913:45: note: format string is defined here
3913 | "%s: jbd2_start: %ld blocks, ino %lu; err %d\n",
| ~~^
| |
| long int
| %d
fs/ext4/inode.c: At top level:
fs/ext4/inode.c:4083:46: warning: 'ext4_iomap_aops' defined but not used [-Wunused-const-variable=]
4083 | static const struct address_space_operations ext4_iomap_aops = {
| ^~~~~~~~~~~~~~~
vim +3913 fs/ext4/inode.c
3889
3890 static int ext4_iomap_prepare_ioend(struct iomap_ioend *ioend, int status)
3891 {
3892 handle_t *handle = NULL;
3893 struct inode *inode = ioend->io_inode;
3894 int rsv_blocks;
3895 int ret;
3896
3897 if (ioend->io_type != IOMAP_UNWRITTEN)
3898 return status;
3899
3900 ioend->io_bio->bi_end_io = ext4_iomap_end_bio;
3901
3902 /*
3903 * Reserve enough transaction credits for unwritten extent
3904 * convert processing in end IO.
3905 */
3906 rsv_blocks = 1 + ext4_chunk_trans_blocks(inode,
3907 ioend->io_size >> inode->i_blkbits);
3908 handle = ext4_journal_start_with_reserve(inode,
3909 EXT4_HT_WRITE_PAGE, 0, rsv_blocks);
3910 if (IS_ERR(handle)) {
3911 ret = PTR_ERR(handle);
3912 ext4_msg(inode->i_sb, KERN_CRIT,
> 3913 "%s: jbd2_start: %ld blocks, ino %lu; err %d\n",
3914 __func__, ioend->io_size >> inode->i_blkbits,
3915 inode->i_ino, ret);
3916 return status ? status : ret;
3917 }
3918 if (ext4_handle_valid(handle)) {
3919 ioend->io_private = handle->h_rsv_handle;
3920 handle->h_rsv_handle = NULL;
3921 }
3922 ext4_journal_stop(handle);
3923
3924 return status;
3925 }
3926
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-24 15:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 12:51 [RFC PATCH 00/18] ext4: use iomap for regular file's buffered IO path and enable large foilo Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 01/18] ext4: introduce ext4_es_skip_hole_extent() to skip hole extents Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 02/18] ext4: make ext4_es_lookup_extent() return the next extent if not found Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 03/18] ext4: correct the hole length returned by ext4_map_blocks() Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 04/18] ext4: add a hole extent entry in cache after punch Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 05/18] ext4: make ext4_map_blocks() distinguish delayed only mapping Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 06/18] ext4: make ext4_set_iomap() recognize IOMAP_DELALLOC mapping type Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 07/18] ext4: allow reserving multi-delayed blocks Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 08/18] ext4: add a new iomap aops for regular file's buffered IO path Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 09/18] ext4: implement buffered read iomap path Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 10/18] ext4: implement buffered write " Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 11/18] iomap: add a fs private parameter to iomap_ioend Zhang Yi
2023-11-23 15:36 ` Christoph Hellwig
2023-11-24 1:36 ` Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 12/18] iomap: don't increase i_size if it's not a write operation Zhang Yi
2023-11-23 15:34 ` Christoph Hellwig
2023-11-24 1:41 ` Zhang Yi
2023-11-30 12:26 ` Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 13/18] ext4: impliment writeback iomap path Zhang Yi
2023-11-24 7:56 ` [PATCH RFC " kernel test robot
2023-11-24 15:41 ` kernel test robot [this message]
2023-11-23 12:51 ` [RFC PATCH 14/18] ext4: impliment zero_range " Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 15/18] ext4: writeback partial blocks before zero range Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 16/18] ext4: impliment mmap iomap path Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 17/18] ext4: partial enable iomap for regular file's buffered IO path Zhang Yi
2023-11-24 13:57 ` Zhang Yi
2023-11-23 12:51 ` Zhang Yi
2023-11-23 12:51 ` [RFC PATCH 18/18] ext4: enable large folio for regular file which has been switched to use iomap 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=202311241945.TOPPNdHa-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yi.zhang@huaweicloud.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 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.