From: kernel test robot <lkp@intel.com>
To: Alex Markuze <amarkuze@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ceph-devel@vger.kernel.org
Subject: [ceph-client:tls-tracing-only 10/14] fs/ceph/debugfs.c:420:3: error: call to undeclared function 'rtlog_log_iter_init'; ISO C99 and later do not support implicit function declarations
Date: Fri, 8 Aug 2025 00:09:27 +0200 [thread overview]
Message-ID: <202508080007.MgUCTMaC-lkp@intel.com> (raw)
tree: https://github.com/ceph/ceph-client.git tls-tracing-only
head: ffad14ce035a047cbfda2d38f7ae37b0767de136
commit: 310aa14b5bf4d5ecd1abf6a00782e044f7d76940 [10/14] ceph integration
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250808/202508080007.MgUCTMaC-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250808/202508080007.MgUCTMaC-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/202508080007.MgUCTMaC-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/ceph/debugfs.c:367:19: warning: variable 'seconds' set but not used [-Wunused-but-set-variable]
367 | unsigned long seconds;
| ^
fs/ceph/debugfs.c:416:13: error: use of undeclared identifier 'g_rtlog_logger'
416 | spin_lock(&g_rtlog_logger.lock);
| ^
fs/ceph/debugfs.c:418:28: error: use of undeclared identifier 'g_rtlog_logger'
418 | list_for_each_entry(ctx, &g_rtlog_logger.contexts, list) {
| ^
fs/ceph/debugfs.c:418:28: error: use of undeclared identifier 'g_rtlog_logger'
fs/ceph/debugfs.c:418:28: error: use of undeclared identifier 'g_rtlog_logger'
fs/ceph/debugfs.c:418:28: error: use of undeclared identifier 'g_rtlog_logger'
>> fs/ceph/debugfs.c:420:3: error: call to undeclared function 'rtlog_log_iter_init'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
420 | rtlog_log_iter_init(&iter, &ctx->pf);
| ^
>> fs/ceph/debugfs.c:431:19: error: call to undeclared function 'rtlog_log_iter_next'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
431 | while ((entry = rtlog_log_iter_next(&iter)) != NULL) {
| ^
fs/ceph/debugfs.c:431:17: error: incompatible integer to pointer conversion assigning to 'struct rtlog_log_entry *' from 'int' [-Wint-conversion]
431 | while ((entry = rtlog_log_iter_next(&iter)) != NULL) {
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~
>> fs/ceph/debugfs.c:436:19: error: call to undeclared function 'rtlog_is_valid_kernel_addr'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
436 | if (!entry || !rtlog_is_valid_kernel_addr(entry)) {
| ^
fs/ceph/debugfs.c:423:7: warning: variable 'ctx_entries' set but not used [-Wunused-but-set-variable]
423 | int ctx_entries = 0;
| ^
fs/ceph/debugfs.c:481:15: error: use of undeclared identifier 'g_rtlog_logger'
481 | spin_unlock(&g_rtlog_logger.lock);
| ^
fs/ceph/debugfs.c:502:24: error: use of undeclared identifier 'g_rtlog_logger'
502 | spin_lock_irqsave(&g_rtlog_logger.lock, flags);
| ^
fs/ceph/debugfs.c:506:31: error: use of undeclared identifier 'g_rtlog_logger'
506 | list_for_each_entry(ctx, &g_rtlog_logger.contexts, list) {
| ^
fs/ceph/debugfs.c:506:31: error: use of undeclared identifier 'g_rtlog_logger'
fs/ceph/debugfs.c:506:31: error: use of undeclared identifier 'g_rtlog_logger'
fs/ceph/debugfs.c:506:31: error: use of undeclared identifier 'g_rtlog_logger'
fs/ceph/debugfs.c:516:29: error: use of undeclared identifier 'g_rtlog_logger'
516 | spin_unlock_irqrestore(&g_rtlog_logger.lock, flags);
| ^
2 warnings and 16 errors generated.
vim +/rtlog_log_iter_init +420 fs/ceph/debugfs.c
405
406 static int rtlog_tls_show_internal(struct seq_file *s, void *p)
407 {
408 struct rtlog_tls_ctx *ctx;
409 struct rtlog_log_iter iter;
410 struct rtlog_log_entry *entry;
411 const struct rtlog_source_info *source;
412 int total_entries = 0;
413 int total_contexts = 0;
414
415 /* Lock the logger to safely traverse the contexts list */
> 416 spin_lock(&g_rtlog_logger.lock);
417
> 418 list_for_each_entry(ctx, &g_rtlog_logger.contexts, list) {
419 /* Initialize iterator for this context's pagefrag */
> 420 rtlog_log_iter_init(&iter, &ctx->pf);
421 int pid = ctx->pid;
422 char *comm = ctx->comm;
423 int ctx_entries = 0;
424
425 total_contexts++;
426
427 /* Lock the pagefrag before accessing entries */
428 spin_lock_bh(&ctx->pf.lock);
429
430 /* Iterate through log entries in this context */
> 431 while ((entry = rtlog_log_iter_next(&iter)) != NULL) {
432 char datetime_str[32];
433 char reconstructed_msg[256];
434
435 /* Validate entry before processing */
> 436 if (!entry || !rtlog_is_valid_kernel_addr(entry)) {
437 seq_printf(s, "[%d][%s]: Invalid entry pointer %p\n", pid, comm, entry);
438 break;
439 }
440
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-07 22:09 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=202508080007.MgUCTMaC-lkp@intel.com \
--to=lkp@intel.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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).