From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>, Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
"Darrick J. Wong" <djwong@kernel.org>,
Joanne Koong <joannelkoong@gmail.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
gfs2@lists.linux.dev
Subject: Re: [PATCH 01/14] iomap: header diet
Date: Wed, 9 Jul 2025 17:09:19 +0800 [thread overview]
Message-ID: <202507091656.dMTKUTBY-lkp@intel.com> (raw)
In-Reply-To: <20250708135132.3347932-2-hch@lst.de>
Hi Christoph,
kernel test robot noticed the following build errors:
[auto build test ERROR on brauner-vfs/vfs.all]
[also build test ERROR on xfs-linux/for-next gfs2/for-next linus/master v6.16-rc5 next-20250708]
[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/Christoph-Hellwig/iomap-pass-more-arguments-using-the-iomap-writeback-context/20250708-225155
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20250708135132.3347932-2-hch%40lst.de
patch subject: [PATCH 01/14] iomap: header diet
config: arc-randconfig-001-20250709 (https://download.01.org/0day-ci/archive/20250709/202507091656.dMTKUTBY-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250709/202507091656.dMTKUTBY-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/202507091656.dMTKUTBY-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
fs/iomap/buffered-io.c: In function 'iomap_dirty_folio':
>> fs/iomap/buffered-io.c:642:9: error: implicit declaration of function 'filemap_dirty_folio'; did you mean 'iomap_dirty_folio'? [-Werror=implicit-function-declaration]
return filemap_dirty_folio(mapping, folio);
^~~~~~~~~~~~~~~~~~~
iomap_dirty_folio
fs/iomap/buffered-io.c: In function 'iomap_write_iter':
>> fs/iomap/buffered-io.c:930:58: error: 'BDP_ASYNC' undeclared (first use in this function); did you mean 'I_SYNC'?
unsigned int bdp_flags = (iter->flags & IOMAP_NOWAIT) ? BDP_ASYNC : 0;
^~~~~~~~~
I_SYNC
fs/iomap/buffered-io.c:930:58: note: each undeclared identifier is reported only once for each function it appears in
>> fs/iomap/buffered-io.c:945:12: error: implicit declaration of function 'balance_dirty_pages_ratelimited_flags' [-Werror=implicit-function-declaration]
status = balance_dirty_pages_ratelimited_flags(mapping,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
fs/iomap/buffered-io.c: In function 'iomap_unshare_iter':
>> fs/iomap/buffered-io.c:1309:3: error: implicit declaration of function 'balance_dirty_pages_ratelimited'; did you mean 'pr_alert_ratelimited'? [-Werror=implicit-function-declaration]
balance_dirty_pages_ratelimited(iter->inode->i_mapping);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
pr_alert_ratelimited
fs/iomap/buffered-io.c: In function 'iomap_zero_iter':
>> fs/iomap/buffered-io.c:1376:3: error: implicit declaration of function 'folio_mark_accessed'; did you mean 'folio_wait_locked'? [-Werror=implicit-function-declaration]
folio_mark_accessed(folio);
^~~~~~~~~~~~~~~~~~~
folio_wait_locked
fs/iomap/buffered-io.c: In function 'iomap_alloc_ioend':
fs/iomap/buffered-io.c:1624:26: error: implicit declaration of function 'wbc_to_write_flags'; did you mean 'do_pipe_flags'? [-Werror=implicit-function-declaration]
REQ_OP_WRITE | wbc_to_write_flags(wbc),
^~~~~~~~~~~~~~~~~~
do_pipe_flags
fs/iomap/buffered-io.c:1629:2: error: implicit declaration of function 'wbc_init_bio'; did you mean 'arc_init_IRQ'? [-Werror=implicit-function-declaration]
wbc_init_bio(wbc, bio);
^~~~~~~~~~~~
arc_init_IRQ
fs/iomap/buffered-io.c: In function 'iomap_add_to_ioend':
fs/iomap/buffered-io.c:1748:2: error: implicit declaration of function 'wbc_account_cgroup_owner'; did you mean 'pr_cont_cgroup_name'? [-Werror=implicit-function-declaration]
wbc_account_cgroup_owner(wbc, folio, len);
^~~~~~~~~~~~~~~~~~~~~~~~
pr_cont_cgroup_name
fs/iomap/buffered-io.c: In function 'iomap_writepages':
>> fs/iomap/buffered-io.c:1965:18: error: implicit declaration of function 'writeback_iter'; did you mean 'write_lock_irq'? [-Werror=implicit-function-declaration]
while ((folio = writeback_iter(mapping, wbc, folio, &error)))
^~~~~~~~~~~~~~
write_lock_irq
>> fs/iomap/buffered-io.c:1965:16: warning: assignment to 'struct folio *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
while ((folio = writeback_iter(mapping, wbc, folio, &error)))
^
cc1: some warnings being treated as errors
vim +642 fs/iomap/buffered-io.c
8306a5f5630552 Matthew Wilcox (Oracle 2021-04-28 634)
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 635) bool iomap_dirty_folio(struct address_space *mapping, struct folio *folio)
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 636) {
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 637) struct inode *inode = mapping->host;
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 638) size_t len = folio_size(folio);
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 639)
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 640) ifs_alloc(inode, folio, 0);
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 641) iomap_set_range_dirty(folio, 0, len);
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 @642) return filemap_dirty_folio(mapping, folio);
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 643) }
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 644) EXPORT_SYMBOL_GPL(iomap_dirty_folio);
4ce02c67972211 Ritesh Harjani (IBM 2023-07-10 645)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-09 9:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 13:51 refactor the iomap writeback code v4 Christoph Hellwig
2025-07-08 13:51 ` [PATCH 01/14] iomap: header diet Christoph Hellwig
2025-07-08 19:45 ` Darrick J. Wong
2025-07-08 21:09 ` Joanne Koong
2025-07-09 9:09 ` kernel test robot [this message]
2025-07-09 17:53 ` Joanne Koong
2025-07-08 13:51 ` [PATCH 02/14] iomap: pass more arguments using the iomap writeback context Christoph Hellwig
2025-07-08 19:45 ` Darrick J. Wong
2025-07-08 13:51 ` [PATCH 03/14] iomap: cleanup the pending writeback tracking in iomap_writepage_map_blocks Christoph Hellwig
2025-07-08 13:51 ` [PATCH 04/14] iomap: refactor the writeback interface Christoph Hellwig
2025-07-08 19:44 ` Darrick J. Wong
2025-07-08 13:51 ` [PATCH 05/14] iomap: hide ioends from the generic writeback code Christoph Hellwig
2025-07-08 19:42 ` Darrick J. Wong
2025-07-08 13:51 ` [PATCH 06/14] iomap: add public helpers for uptodate state manipulation Christoph Hellwig
2025-07-08 13:51 ` [PATCH 07/14] iomap: move all ioend handling to ioend.c Christoph Hellwig
2025-07-08 13:51 ` [PATCH 08/14] iomap: rename iomap_writepage_map to iomap_writeback_folio Christoph Hellwig
2025-07-08 21:12 ` Joanne Koong
2025-07-08 13:51 ` [PATCH 09/14] iomap: move folio_unlock out of iomap_writeback_folio Christoph Hellwig
2025-07-08 13:51 ` [PATCH 10/14] iomap: export iomap_writeback_folio Christoph Hellwig
2025-07-08 13:51 ` [PATCH 11/14] iomap: replace iomap_folio_ops with iomap_write_ops Christoph Hellwig
2025-07-08 13:51 ` [PATCH 12/14] iomap: improve argument passing to iomap_read_folio_sync Christoph Hellwig
2025-07-08 19:40 ` Darrick J. Wong
2025-07-08 21:23 ` Joanne Koong
2025-07-08 13:51 ` [PATCH 13/14] iomap: add read_folio_range() handler for buffered writes Christoph Hellwig
2025-07-08 13:51 ` [PATCH 14/14] iomap: build the writeback code without CONFIG_BLOCK Christoph Hellwig
2025-07-08 21:27 ` Joanne Koong
2025-07-08 21:30 ` refactor the iomap writeback code v4 Joanne Koong
-- strict thread matches above, loose matches on Subject: below --
2025-07-10 13:33 refactor the iomap writeback code v5 Christoph Hellwig
2025-07-10 13:33 ` [PATCH 01/14] iomap: header diet Christoph Hellwig
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=202507091656.dMTKUTBY-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=hch@lst.de \
--cc=joannelkoong@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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).