All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] riscv: add VMAP_STACK overflow detection
Date: Fri, 07 May 2021 20:00:31 +0800	[thread overview]
Message-ID: <202105071955.PiPFbB3I-lkp@intel.com> (raw)
In-Reply-To: <20210507092509.41346-1-tongtiangen@huawei.com>

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

Hi Tong,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on v5.12]
[also build test WARNING on next-20210507]
[cannot apply to linus/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Tong-Tiangen/riscv-add-VMAP_STACK-overflow-detection/20210507-171736
base:    9f4ad9e425a1d3b6a34617b8ea226d56a119a717
config: riscv-randconfig-r015-20210507 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project a3a8a1a15b524d91b5308db68e9d293b34cd88dd)
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
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/0day-ci/linux/commit/60d8a3da002bf59ec0abeb88403dbb11cf31583f
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Tong-Tiangen/riscv-add-VMAP_STACK-overflow-detection/20210507-171736
        git checkout 60d8a3da002bf59ec0abeb88403dbb11cf31583f
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=riscv 

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

All warnings (new ones prefixed by >>):

>> arch/riscv/kernel/traps.c:212:26: warning: no previous prototype for function 'get_overflow_stack' [-Wmissing-prototypes]
   asmlinkage unsigned long get_overflow_stack(void)
                            ^
   arch/riscv/kernel/traps.c:212:12: note: declare 'static' if the function is not intended to be used outside of this translation unit
   asmlinkage unsigned long get_overflow_stack(void)
              ^
              static 
>> arch/riscv/kernel/traps.c:218:17: warning: no previous prototype for function 'handle_bad_stack' [-Wmissing-prototypes]
   asmlinkage void handle_bad_stack(struct pt_regs *regs)
                   ^
   arch/riscv/kernel/traps.c:218:12: note: declare 'static' if the function is not intended to be used outside of this translation unit
   asmlinkage void handle_bad_stack(struct pt_regs *regs)
              ^
              static 
   2 warnings generated.


vim +/get_overflow_stack +212 arch/riscv/kernel/traps.c

   203	
   204	#ifdef CONFIG_VMAP_STACK
   205	DEFINE_PER_CPU(unsigned long [OVERFLOW_STACK_SIZE/sizeof(long)], overflow_stack)
   206			__aligned(16);
   207	/*
   208	 * shadow stack, handled_ kernel_ stack_ overflow(in kernel/entry.S) is used
   209	 * to get per-cpu overflow stack(get_overflow_stack).
   210	 */
   211	long shadow_stack[SHADOW_OVERFLOW_STACK_SIZE/sizeof(long)];
 > 212	asmlinkage unsigned long get_overflow_stack(void)
   213	{
   214		return (unsigned long)this_cpu_ptr(overflow_stack) +
   215			OVERFLOW_STACK_SIZE;
   216	}
   217	
 > 218	asmlinkage void handle_bad_stack(struct pt_regs *regs)

---
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: 31413 bytes --]

  reply	other threads:[~2021-05-07 12:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07  9:25 [RFC PATCH] riscv: add VMAP_STACK overflow detection Tong Tiangen
2021-05-07  9:25 ` Tong Tiangen
2021-05-07 12:00 ` kernel test robot [this message]
2021-05-07 12:37 ` kernel test robot
2021-05-07 13:22 ` kernel test robot
2021-05-23  1:49 ` Palmer Dabbelt
2021-05-23  1:49   ` Palmer Dabbelt
2021-05-24 13:51   ` tongtiangen
2021-05-24 13:51     ` tongtiangen

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=202105071955.PiPFbB3I-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.