All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 2605/2770] mm/kasan/report.c:233:2: error: implicit declaration of function 'dump_stack_lvl'; did you mean 'dump_stack'?
Date: Thu, 13 May 2021 17:03:28 +0800	[thread overview]
Message-ID: <202105131720.yP4kfiAi-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2553 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   ec2618180c3450d06a6a4ba951d4c9a2c689b517
commit: 9fb7170c7fba3f6099d57b3d028c500df70a9980 [2605/2770] kasan: use dump_stack_lvl(KERN_ERR) to print stacks
config: arm64-randconfig-r014-20210513 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9fb7170c7fba3f6099d57b3d028c500df70a9980
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 9fb7170c7fba3f6099d57b3d028c500df70a9980
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   mm/kasan/report.c: In function 'print_address_description':
>> mm/kasan/report.c:233:2: error: implicit declaration of function 'dump_stack_lvl'; did you mean 'dump_stack'? [-Werror=implicit-function-declaration]
     233 |  dump_stack_lvl(KERN_ERR);
         |  ^~~~~~~~~~~~~~
         |  dump_stack
   cc1: some warnings being treated as errors


vim +233 mm/kasan/report.c

   228	
   229	static void print_address_description(void *addr, u8 tag)
   230	{
   231		struct page *page = kasan_addr_to_page(addr);
   232	
 > 233		dump_stack_lvl(KERN_ERR);
   234		pr_err("\n");
   235	
   236		if (page && PageSlab(page)) {
   237			struct kmem_cache *cache = page->slab_cache;
   238			void *object = nearest_obj(cache, page,	addr);
   239	
   240			describe_object(cache, object, addr, tag);
   241		}
   242	
   243		if (kernel_or_module_addr(addr) && !init_task_stack_addr(addr)) {
   244			pr_err("The buggy address belongs to the variable:\n");
   245			pr_err(" %pS\n", addr);
   246		}
   247	
   248		if (page) {
   249			pr_err("The buggy address belongs to the page:\n");
   250			dump_page(page, "kasan: bad access detected");
   251		}
   252	
   253		kasan_print_address_stack_frame(addr);
   254	}
   255	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34099 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Alexander Potapenko <glider@google.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Marco Elver <elver@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 2605/2770] mm/kasan/report.c:233:2: error: implicit declaration of function 'dump_stack_lvl'; did you mean 'dump_stack'?
Date: Thu, 13 May 2021 17:03:28 +0800	[thread overview]
Message-ID: <202105131720.yP4kfiAi-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2489 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   ec2618180c3450d06a6a4ba951d4c9a2c689b517
commit: 9fb7170c7fba3f6099d57b3d028c500df70a9980 [2605/2770] kasan: use dump_stack_lvl(KERN_ERR) to print stacks
config: arm64-randconfig-r014-20210513 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9fb7170c7fba3f6099d57b3d028c500df70a9980
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 9fb7170c7fba3f6099d57b3d028c500df70a9980
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   mm/kasan/report.c: In function 'print_address_description':
>> mm/kasan/report.c:233:2: error: implicit declaration of function 'dump_stack_lvl'; did you mean 'dump_stack'? [-Werror=implicit-function-declaration]
     233 |  dump_stack_lvl(KERN_ERR);
         |  ^~~~~~~~~~~~~~
         |  dump_stack
   cc1: some warnings being treated as errors


vim +233 mm/kasan/report.c

   228	
   229	static void print_address_description(void *addr, u8 tag)
   230	{
   231		struct page *page = kasan_addr_to_page(addr);
   232	
 > 233		dump_stack_lvl(KERN_ERR);
   234		pr_err("\n");
   235	
   236		if (page && PageSlab(page)) {
   237			struct kmem_cache *cache = page->slab_cache;
   238			void *object = nearest_obj(cache, page,	addr);
   239	
   240			describe_object(cache, object, addr, tag);
   241		}
   242	
   243		if (kernel_or_module_addr(addr) && !init_task_stack_addr(addr)) {
   244			pr_err("The buggy address belongs to the variable:\n");
   245			pr_err(" %pS\n", addr);
   246		}
   247	
   248		if (page) {
   249			pr_err("The buggy address belongs to the page:\n");
   250			dump_page(page, "kasan: bad access detected");
   251		}
   252	
   253		kasan_print_address_stack_frame(addr);
   254	}
   255	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34099 bytes --]

             reply	other threads:[~2021-05-13  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13  9:03 kernel test robot [this message]
2021-05-13  9:03 ` [linux-next:master 2605/2770] mm/kasan/report.c:233:2: error: implicit declaration of function 'dump_stack_lvl'; did you mean 'dump_stack'? kernel test robot
2021-05-13 11:14 ` [PATCH] fix for "printk: introduce dump_stack_lvl()" Marco Elver
2021-05-13 11:14   ` Marco Elver
2021-05-13 11:20   ` Alexander Potapenko
2021-05-13 11:20     ` Alexander Potapenko

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=202105131720.yP4kfiAi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.