mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peter Collingbourne <pcc@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: [ammarfaizi2-block:arm64/linux/for-next/mte 2/6] include/linux/kasan-enabled.h:7:26: error: a parameter list without types is only allowed in a function definition
Date: Sat, 26 Feb 2022 10:32:51 +0800	[thread overview]
Message-ID: <202202261019.v5uTU7PH-lkp@intel.com> (raw)

tree:   https://github.com/ammarfaizi2/linux-block arm64/linux/for-next/mte
head:   766121ba5de38a6f67980ec24a6af76c55def100
commit: 38ddf7dafaeaf3fcdea65b3b4dfb06b4bcd9cc15 [2/6] arm64: mte: avoid clearing PSTATE.TCO on entry unless necessary
config: arm64-randconfig-r011-20220225 (https://download.01.org/0day-ci/archive/20220226/202202261019.v5uTU7PH-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d271fc04d5b97b12e6b797c6067d3c96a8d7470e)
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 arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/ammarfaizi2/linux-block/commit/38ddf7dafaeaf3fcdea65b3b4dfb06b4bcd9cc15
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block arm64/linux/for-next/mte
        git checkout 38ddf7dafaeaf3fcdea65b3b4dfb06b4bcd9cc15
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/tty/serial/

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

All error/warnings (new ones prefixed by >>):

   In file included from drivers/tty/serial/earlycon.c:16:
   In file included from include/linux/io.h:13:
   In file included from arch/arm64/include/asm/io.h:12:
   In file included from include/linux/pgtable.h:6:
   In file included from arch/arm64/include/asm/pgtable.h:12:
   In file included from arch/arm64/include/asm/mte.h:14:
>> include/linux/kasan-enabled.h:7:1: warning: declaration specifier missing, defaulting to 'int'
   DECLARE_STATIC_KEY_FALSE(kasan_flag_enabled);
   ^
   int
>> include/linux/kasan-enabled.h:7:26: error: a parameter list without types is only allowed in a function definition
   DECLARE_STATIC_KEY_FALSE(kasan_flag_enabled);
                            ^
>> include/linux/kasan-enabled.h:11:9: error: implicit declaration of function 'static_branch_likely' [-Werror,-Wimplicit-function-declaration]
           return static_branch_likely(&kasan_flag_enabled);
                  ^
>> include/linux/kasan-enabled.h:11:31: error: use of undeclared identifier 'kasan_flag_enabled'; did you mean 'kasan_enabled'?
           return static_branch_likely(&kasan_flag_enabled);
                                        ^~~~~~~~~~~~~~~~~~
                                        kasan_enabled
   include/linux/kasan-enabled.h:9:29: note: 'kasan_enabled' declared here
   static __always_inline bool kasan_enabled(void)
                               ^
   1 warning and 3 errors generated.


vim +7 include/linux/kasan-enabled.h

f9b5e46f4097eb2 Peter Collingbourne 2022-02-18   6  
f9b5e46f4097eb2 Peter Collingbourne 2022-02-18  @7  DECLARE_STATIC_KEY_FALSE(kasan_flag_enabled);
f9b5e46f4097eb2 Peter Collingbourne 2022-02-18   8  
f9b5e46f4097eb2 Peter Collingbourne 2022-02-18   9  static __always_inline bool kasan_enabled(void)
f9b5e46f4097eb2 Peter Collingbourne 2022-02-18  10  {
f9b5e46f4097eb2 Peter Collingbourne 2022-02-18 @11  	return static_branch_likely(&kasan_flag_enabled);
f9b5e46f4097eb2 Peter Collingbourne 2022-02-18  12  }
f9b5e46f4097eb2 Peter Collingbourne 2022-02-18  13  

:::::: The code at line 7 was first introduced by commit
:::::: f9b5e46f4097eb298f68e5b02f70697a90a44739 kasan: split kasan_*enabled() functions into a separate header

:::::: TO: Peter Collingbourne <pcc@google.com>
:::::: CC: Will Deacon <will@kernel.org>

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

                 reply	other threads:[~2022-02-26  2:33 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=202202261019.v5uTU7PH-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=pcc@google.com \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®