public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [peterz-queue:x86/wip.ibt 25/42] arch/x86/include/asm/ibt.h:63:15: error: unknown type name 'u64'
Date: Thu, 24 Feb 2022 12:44:34 +0800	[thread overview]
Message-ID: <202202241208.n3vmbrZZ-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/wip.ibt
head:   27b6438f414b6a37b60dcd90c8980397586d49db
commit: 3910f0559d1462af4095e3e1248686dd2d74eb99 [25/42] x86: Disable IBT around firmware
config: um-i386_defconfig (https://download.01.org/0day-ci/archive/20220224/202202241208.n3vmbrZZ-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=3910f0559d1462af4095e3e1248686dd2d74eb99
        git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
        git fetch --no-tags peterz-queue x86/wip.ibt
        git checkout 3910f0559d1462af4095e3e1248686dd2d74eb99
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=um SUBARCH=i386 SHELL=/bin/bash

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/x86/include/asm/linkage.h:6,
                    from include/linux/linkage.h:8,
                    from include/linux/fs.h:5,
                    from include/linux/tty.h:5,
                    from arch/um/drivers/stdio_console.c:7:
   arch/x86/include/asm/ibt.h:61:15: error: unknown type name 'bool'
      61 | static inline bool is_endbr(unsigned int val) { return false; }
         |               ^~~~
>> arch/x86/include/asm/ibt.h:63:15: error: unknown type name 'u64'
      63 | static inline u64 ibt_save(void) { return 0; }
         |               ^~~
   arch/x86/include/asm/ibt.h:64:32: error: unknown type name 'u64'
      64 | static inline void ibt_restore(u64 save) { }
         |                                ^~~
--
   In file included from arch/x86/include/asm/linkage.h:6,
                    from include/linux/linkage.h:8,
                    from include/linux/fs.h:5,
                    from arch/um/drivers/ssl.c:6:
   arch/x86/include/asm/ibt.h:61:15: error: unknown type name 'bool'
      61 | static inline bool is_endbr(unsigned int val) { return false; }
         |               ^~~~
   arch/x86/include/asm/ibt.h: In function 'is_endbr':
   arch/x86/include/asm/ibt.h:61:56: error: 'false' undeclared (first use in this function)
      61 | static inline bool is_endbr(unsigned int val) { return false; }
         |                                                        ^~~~~
   arch/x86/include/asm/ibt.h:61:56: note: each undeclared identifier is reported only once for each function it appears in
   arch/x86/include/asm/ibt.h: At top level:
>> arch/x86/include/asm/ibt.h:63:15: error: unknown type name 'u64'
      63 | static inline u64 ibt_save(void) { return 0; }
         |               ^~~
   arch/x86/include/asm/ibt.h:64:32: error: unknown type name 'u64'
      64 | static inline void ibt_restore(u64 save) { }
         |                                ^~~
--
   In file included from arch/x86/include/asm/linkage.h:6,
                    from include/linux/linkage.h:8,
                    from include/linux/fs.h:5,
                    from fs/proc/meminfo.c:2:
   arch/x86/include/asm/ibt.h:61:15: error: unknown type name 'bool'
      61 | static inline bool is_endbr(unsigned int val) { return false; }
         |               ^~~~
   arch/x86/include/asm/ibt.h: In function 'is_endbr':
   arch/x86/include/asm/ibt.h:61:56: error: 'false' undeclared (first use in this function)
      61 | static inline bool is_endbr(unsigned int val) { return false; }
         |                                                        ^~~~~
   arch/x86/include/asm/ibt.h:61:56: note: each undeclared identifier is reported only once for each function it appears in
   arch/x86/include/asm/ibt.h: At top level:
>> arch/x86/include/asm/ibt.h:63:15: error: unknown type name 'u64'
      63 | static inline u64 ibt_save(void) { return 0; }
         |               ^~~
   arch/x86/include/asm/ibt.h:64:32: error: unknown type name 'u64'
      64 | static inline void ibt_restore(u64 save) { }
         |                                ^~~
   fs/proc/meminfo.c:22:28: warning: no previous prototype for 'arch_report_meminfo' [-Wmissing-prototypes]
      22 | void __attribute__((weak)) arch_report_meminfo(struct seq_file *m)
         |                            ^~~~~~~~~~~~~~~~~~~


vim +/u64 +63 arch/x86/include/asm/ibt.h

    60	
  > 61	static inline bool is_endbr(unsigned int val) { return false; }
    62	
  > 63	static inline u64 ibt_save(void) { return 0; }
    64	static inline void ibt_restore(u64 save) { }
    65	

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

                 reply	other threads:[~2022-02-24  4:45 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=202202241208.n3vmbrZZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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