linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Alexander Potapenko <glider@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 11672/11713] mm/kasan/report_sw_tags.c:58:22: error: implicit declaration of function 'object_is_on_stack'
Date: Thu, 10 Mar 2022 13:45:21 +0800	[thread overview]
Message-ID: <202203101313.LWqhjLOB-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   4e7a74a6856f8613dab9794da4b5cfb8fd54fb8c
commit: 15b4f8fb062a6f681b2c84cef2da7d8af4629230 [11672/11713] kasan: print basic stack frame info for SW_TAGS
config: arm64-randconfig-r034-20220309 (https://download.01.org/0day-ci/archive/20220310/202203101313.LWqhjLOB-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.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=15b4f8fb062a6f681b2c84cef2da7d8af4629230
        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 15b4f8fb062a6f681b2c84cef2da7d8af4629230
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash mm/kasan/

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 >>):

   In file included from arch/arm64/include/asm/bug.h:26,
                    from include/linux/bug.h:5,
                    from include/linux/cpumask.h:14,
                    from include/linux/interrupt.h:8,
                    from include/linux/trace_recursion.h:5,
                    from include/linux/ftrace.h:10,
                    from mm/kasan/report_sw_tags.c:13:
   mm/kasan/report_sw_tags.c: In function 'kasan_print_address_stack_frame':
>> mm/kasan/report_sw_tags.c:58:22: error: implicit declaration of function 'object_is_on_stack' [-Werror=implicit-function-declaration]
      58 |         if (WARN_ON(!object_is_on_stack(addr)))
         |                      ^~~~~~~~~~~~~~~~~~
   include/asm-generic/bug.h:166:32: note: in definition of macro 'WARN_ON'
     166 |         int __ret_warn_on = !!(condition);                              \
         |                                ^~~~~~~~~
   cc1: some warnings being treated as errors


vim +/object_is_on_stack +58 mm/kasan/report_sw_tags.c

    54	
    55	#ifdef CONFIG_KASAN_STACK
    56	void kasan_print_address_stack_frame(const void *addr)
    57	{
  > 58		if (WARN_ON(!object_is_on_stack(addr)))

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


                 reply	other threads:[~2022-03-10  5:46 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=202203101313.LWqhjLOB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=glider@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox