From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Gu Bowen <gubowen5@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:openEuler-1.0-LTS 1941/1941] mm/kmemleak.c:434:4: error: implicit declaration of function 'printk_safe_exit'; did you mean 'printk_nmi_exit'?
Date: Sat, 13 Dec 2025 05:44:24 +0800 [thread overview]
Message-ID: <202512130502.2LxTdCek-lkp@intel.com> (raw)
Hi Gu,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: df8d11fbcbb07177c2500e63d7f5a36063977596
commit: 38f093f2876aaa0dd46e11d638e8d2a263f38199 [1941/1941] mm: Fix possible deadlock in console_trylock_spinning
config: arm64-randconfig-002-20251212 (https://download.01.org/0day-ci/archive/20251213/202512130502.2LxTdCek-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512130502.2LxTdCek-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/202512130502.2LxTdCek-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/kmemleak.c: In function 'lookup_object':
mm/kmemleak.c:430:4: error: implicit declaration of function 'printk_safe_enter'; did you mean 'printk_nmi_enter'? [-Werror=implicit-function-declaration]
printk_safe_enter();
^~~~~~~~~~~~~~~~~
printk_nmi_enter
>> mm/kmemleak.c:434:4: error: implicit declaration of function 'printk_safe_exit'; did you mean 'printk_nmi_exit'? [-Werror=implicit-function-declaration]
printk_safe_exit();
^~~~~~~~~~~~~~~~
printk_nmi_exit
cc1: some warnings being treated as errors
vim +434 mm/kmemleak.c
405
406 /*
407 * Look-up a memory block metadata (kmemleak_object) in the object search
408 * tree based on a pointer value. If alias is 0, only values pointing to the
409 * beginning of the memory block are allowed. The kmemleak_lock must be held
410 * when calling this function.
411 */
412 static struct kmemleak_object *lookup_object(unsigned long ptr, int alias)
413 {
414 struct rb_node *rb = object_tree_root.rb_node;
415
416 while (rb) {
417 struct kmemleak_object *object =
418 rb_entry(rb, struct kmemleak_object, rb_node);
419 if (ptr < object->pointer)
420 rb = object->rb_node.rb_left;
421 else if (object->pointer + object->size <= ptr)
422 rb = object->rb_node.rb_right;
423 else if (object->pointer == ptr || alias)
424 return object;
425 else {
426 /*
427 * Printk deferring due to the kmemleak_lock held.
428 * This is done to avoid deadlock.
429 */
430 printk_safe_enter();
431 kmemleak_warn("Found object by alias at 0x%08lx\n",
432 ptr);
433 dump_object_info(object);
> 434 printk_safe_exit();
435
436 break;
437 }
438 }
439 return NULL;
440 }
441
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-12 21:44 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=202512130502.2LxTdCek-lkp@intel.com \
--to=lkp@intel.com \
--cc=gubowen5@huawei.com \
--cc=kernel@openeuler.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.