From: kernel test robot <lkp@intel.com>
To: "Harry Yoo (Oracle)" <harry@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [harry:kfree_rcu_nolock-v3r2 2/9] lib/tests/slub_kunit.c:410:9: error: implicit declaration of function 'test_nolock'
Date: Tue, 16 Jun 2026 16:42:34 +0800 [thread overview]
Message-ID: <202606161614.v4taQKBs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/harry/linux.git kfree_rcu_nolock-v3r2
head: ae8ee8383751a6087097cfb02110c1f489b1eace
commit: fb5395cf57a5aff4eef4ea985d132edb5fcb373d [2/9] mm/slab, slub_kunit: register kprobe to trigger _nolock APIs
config: arc-randconfig-r132-20260616 (https://download.01.org/0day-ci/archive/20260616/202606161614.v4taQKBs-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 13.4.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260616/202606161614.v4taQKBs-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/202606161614.v4taQKBs-lkp@intel.com/
All errors (new ones prefixed by >>):
lib/tests/slub_kunit.c: In function 'slab_kprobe_pre_handler':
>> lib/tests/slub_kunit.c:410:9: error: implicit declaration of function 'test_nolock' [-Werror=implicit-function-declaration]
410 | test_nolock(ctx);
| ^~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/test_nolock +410 lib/tests/slub_kunit.c
403
404 #if defined(CONFIG_KPROBES) && defined(CONFIG_SMP)
405 static int slab_kprobe_pre_handler(struct kprobe *p, struct pt_regs *regs)
406 {
407 struct test_nolock_context *ctx;
408
409 ctx = container_of(p, struct test_nolock_context, kprobe);
> 410 test_nolock(ctx);
411 return 0;
412 }
413
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-16 8:42 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=202606161614.v4taQKBs-lkp@intel.com \
--to=lkp@intel.com \
--cc=harry@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.