From: kernel test robot <lkp@intel.com>
To: Chao Yu <chao@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chao:bugfix/common 7/7] fs/f2fs/data.c:2647:29: error: 'next_pgofs' undeclared
Date: Sat, 10 Jan 2026 19:10:46 +0800 [thread overview]
Message-ID: <202601101924.SAYVUGQa-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
head: 261bd0007c481171f11979ad38d62af7725d56df
commit: 261bd0007c481171f11979ad38d62af7725d56df [7/7] f2fs: avoid f2fs_map_blocks() for hole in readpages
config: i386-randconfig-012-20260110 (https://download.01.org/0day-ci/archive/20260110/202601101924.SAYVUGQa-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260110/202601101924.SAYVUGQa-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/202601101924.SAYVUGQa-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/f2fs/data.c: In function 'f2fs_get_read_data_folio':
fs/f2fs/data.c:1274:31: warning: unused variable 'mapping' [-Wunused-variable]
1274 | struct address_space *mapping = inode->i_mapping;
| ^~~~~~~
fs/f2fs/data.c: In function 'f2fs_mpage_readpages':
>> fs/f2fs/data.c:2647:29: error: 'next_pgofs' undeclared (first use in this function)
2647 | map.m_next_pgofs = &next_pgofs;
| ^~~~~~~~~~
fs/f2fs/data.c:2647:29: note: each undeclared identifier is reported only once for each function it appears in
vim +/next_pgofs +2647 fs/f2fs/data.c
2642
2643 map.m_pblk = 0;
2644 map.m_lblk = 0;
2645 map.m_len = 0;
2646 map.m_flags = 0;
> 2647 map.m_next_pgofs = &next_pgofs;
2648 map.m_next_extent = NULL;
2649 map.m_seg_type = NO_CHECK_TYPE;
2650 map.m_may_create = false;
2651
2652 for (; nr_pages; nr_pages--) {
2653 if (rac) {
2654 folio = readahead_folio(rac);
2655 prefetchw(&folio->flags);
2656 }
2657
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-10 11: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=202601101924.SAYVUGQa-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@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 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.