public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>,
	Valentin Schneider <vschneid@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 3/3] objtool: Add noinstr validation for static branches/calls
Date: Mon, 25 Nov 2024 15:08:13 +0800	[thread overview]
Message-ID: <202411251459.P7KctSbw-lkp@intel.com> (raw)
In-Reply-To: <b5746646456eb030673cdb62c23d69ed83c2702a.1732326588.git.jpoimboe@kernel.org>

Hi Josh,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.12 next-20241122]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Josh-Poimboeuf/jump_label-Add-annotations-for-validating-noinstr-usage/20241125-105905
base:   linus/master
patch link:    https://lore.kernel.org/r/b5746646456eb030673cdb62c23d69ed83c2702a.1732326588.git.jpoimboe%40kernel.org
patch subject: [PATCH 3/3] objtool: Add noinstr validation for static branches/calls
config: powerpc-motionpro_defconfig (https://download.01.org/0day-ci/archive/20241125/202411251459.P7KctSbw-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241125/202411251459.P7KctSbw-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/202411251459.P7KctSbw-lkp@intel.com/

All errors (new ones prefixed by >>):

>> init/main.c:821:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
     821 | DEFINE_STATIC_KEY_MAYBE_RO(CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT,
         | ^
   include/linux/jump_label.h:430:2: note: expanded from macro 'DEFINE_STATIC_KEY_MAYBE_RO'
     430 |         __PASTE(_DEFINE_STATIC_KEY_RO_, IS_ENABLED(cfg))(name)
         |         ^
   include/linux/compiler_types.h:84:22: note: expanded from macro '__PASTE'
      84 | #define __PASTE(a,b) ___PASTE(a,b)
         |                      ^
   include/linux/compiler_types.h:83:23: note: expanded from macro '___PASTE'
      83 | #define ___PASTE(a,b) a##b
         |                       ^
   <scratch space>:51:1: note: expanded from here
      51 | _DEFINE_STATIC_KEY_RO_0
         | ^
   include/linux/jump_label.h:428:39: note: expanded from macro '_DEFINE_STATIC_KEY_RO_0'
     428 | #define _DEFINE_STATIC_KEY_RO_0(name)   DEFINE_STATIC_KEY_FALSE_RO(name)
         |                                         ^
   include/linux/jump_label.h:388:2: note: expanded from macro 'DEFINE_STATIC_KEY_FALSE_RO'
     388 |         ANNOTATE_NOINSTR_ALLOWED(name)
         |         ^
>> init/main.c:822:7: error: a parameter list without types is only allowed in a function definition
     822 |                            randomize_kstack_offset);
         |                            ^
   2 errors generated.


vim +/int +821 init/main.c

4e37958d1288ce Steven Rostedt (VMware  2018-03-26  819) 
8cb37a5974a485 Marco Elver             2022-01-31  820  #ifdef CONFIG_RANDOMIZE_KSTACK_OFFSET
39218ff4c625db Kees Cook               2021-04-01 @821  DEFINE_STATIC_KEY_MAYBE_RO(CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT,
39218ff4c625db Kees Cook               2021-04-01 @822  			   randomize_kstack_offset);
39218ff4c625db Kees Cook               2021-04-01  823  DEFINE_PER_CPU(u32, kstack_offset);
39218ff4c625db Kees Cook               2021-04-01  824  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-11-25  7:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23  1:52 [PATCH 0/3] objtool: noinstr validation for static branches/calls Josh Poimboeuf
2024-11-23  1:52 ` [PATCH 1/3] jump_label: Add annotations for validating noinstr usage Josh Poimboeuf
2024-11-23  1:54   ` Josh Poimboeuf
2024-11-23  1:52 ` [PATCH 2/3] static_call: Add read-only-after-init static calls Josh Poimboeuf
2024-11-23  1:52 ` [PATCH 3/3] objtool: Add noinstr validation for static branches/calls Josh Poimboeuf
2024-11-25  7:08   ` kernel test robot [this message]
2024-11-25  8:00   ` kernel test robot
2024-11-25 10:47   ` kernel test robot

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=202411251459.P7KctSbw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=vschneid@redhat.com \
    /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