From: kernel test robot <lkp@intel.com>
To: huang zheng <huangzheng9869@gmail.com>,
jaegeuk@kernel.org, chao@kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, huangzheng1@xiaomi.com,
Huang Zheng <huangzheng9869@gmail.com>
Subject: Re: [PATCH v2] f2fs: add checkpoint step timing statistics to debugfs
Date: Tue, 17 Nov 2026 00:24:35 +0800 [thread overview]
Message-ID: <202611170005.Q9ISJ71Q-lkp@intel.com> (raw)
In-Reply-To: <20261116095011.2868219-1-huangzheng9869@gmail.com>
Hi huang,
kernel test robot noticed the following build errors:
[auto build test ERROR on jaegeuk-f2fs/dev-test]
[also build test ERROR on jaegeuk-f2fs/dev linus/master v7.4-rc3 next-20261113]
[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/huang-zheng/f2fs-add-checkpoint-step-timing-statistics-to-debugfs/20261116-175011
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link: https://lore.kernel.org/r/20261116095011.2868219-1-huangzheng9869%40gmail.com
patch subject: [PATCH v2] f2fs: add checkpoint step timing statistics to debugfs
config: i386-buildonly-randconfig-1000-20261116 (https://download.01.org/0day-ci/archive/20261117/202611170005.Q9ISJ71Q-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/20261117/202611170005.Q9ISJ71Q-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/202611170005.Q9ISJ71Q-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/f2fs/checkpoint.c: In function 'check_cp_time':
>> fs/f2fs/checkpoint.c:1744:17: error: implicit declaration of function 'update_cp_stats'; did you mean 'update_ckpt_flags'? [-Wimplicit-function-declaration]
1744 | update_cp_stats(sbi, cpc);
| ^~~~~~~~~~~~~~~
| update_ckpt_flags
vim +1744 fs/f2fs/checkpoint.c
1732
1733 static inline void check_cp_time(struct f2fs_sb_info *sbi, struct cp_control *cpc)
1734 {
1735 unsigned long long sb_diff, cur_diff;
1736 enum cp_time ct;
1737
1738 sb_diff = (u64)ktime_ms_delta(sbi->cp_stats.times[CP_TIME_END],
1739 sbi->cp_stats.times[CP_TIME_START]);
1740 cur_diff = (u64)ktime_ms_delta(cpc->stats.times[CP_TIME_END],
1741 cpc->stats.times[CP_TIME_START]);
1742
1743 if (cur_diff > sb_diff) {
> 1744 update_cp_stats(sbi, cpc);
1745 if (cur_diff < CP_LONG_LATENCY_THRESHOLD)
1746 return;
1747
1748 f2fs_warn(sbi, "checkpoint was blocked for %llu ms", cur_diff);
1749 for (ct = CP_TIME_START; ct < CP_TIME_MAX - 1; ct++)
1750 f2fs_warn(sbi, "Step#%d: %llu ms", ct,
1751 (u64)ktime_ms_delta(cpc->stats.times[ct + 1],
1752 cpc->stats.times[ct]));
1753 }
1754 }
1755
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-11-16 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 9:50 huang zheng
2026-11-16 16:24 ` kernel test robot [this message]
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=202611170005.Q9ISJ71Q-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=huangzheng1@xiaomi.com \
--cc=huangzheng9869@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®