All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [jpoimboe:objtool-run 14/29] vmlinux.o: warning: objtool: do_syscall_64()+0x1a: .noinstr.text+0x1a: call to static_key_count() leaves .noinstr.text section
Date: Fri, 15 Apr 2022 11:27:53 +0800	[thread overview]
Message-ID: <202204151123.1XH0Rak6-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: linux-kernel@vger.kernel.org
TO: Josh Poimboeuf <jpoimboe@redhat.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git objtool-run
head:   47d3f4f7a72524799c1f646713e2377e3c4e239f
commit: f27083b059ff86b9c4c7a64c7afa46fd9249b6c3 [14/29] objtool: Add sec+offset to warnings
config: x86_64-randconfig-a001 (https://download.01.org/0day-ci/archive/20220415/202204151123.1XH0Rak6-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 6b7e6ea489f6dd45a9b0da9ac20871560917b9b0)
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/jpoimboe/linux.git/commit/?id=f27083b059ff86b9c4c7a64c7afa46fd9249b6c3
        git remote add jpoimboe https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git
        git fetch --no-tags jpoimboe objtool-run
        git checkout f27083b059ff86b9c4c7a64c7afa46fd9249b6c3
        # 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=x86_64 SHELL=/bin/bash

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

>> vmlinux.o: warning: objtool: do_syscall_64()+0x1a: .noinstr.text+0x1a: call to static_key_count() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: do_int80_syscall_32()+0x27: .noinstr.text+0xbc: call to static_key_count() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: __do_fast_syscall_32()+0x29: .noinstr.text+0x1ca: call to static_key_count() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: fixup_bad_iret()+0x21: .noinstr.text+0xbdf: call to memset() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: in_task_stack()+0xc: .noinstr.text+0x12ec: call to task_stack_page() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: in_entry_stack()+0x9: .noinstr.text+0x1331: call to cpu_entry_stack() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: enter_from_user_mode()+0x2e: .noinstr.text+0x2003: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x36: .noinstr.text+0x2170: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x2e: .noinstr.text+0x244f: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: exit_to_user_mode()+0x26: .noinstr.text+0x25b4: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: syscall_exit_to_user_mode()+0xde: .noinstr.text+0x26da: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x2e: .noinstr.text+0x28c0: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: irqentry_exit_to_user_mode()+0x2d: .noinstr.text+0x2a24: call to __kcsan_check_access() leaves .noinstr.text section

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-04-15  3:28 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=202204151123.1XH0Rak6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    /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.