mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jpoimboe:objtool-run 14/29] vmlinux.o: warning: objtool: exit_to_user_mode()+0x10: .noinstr.text+0x3425: call to static_key_count.constprop.0() leaves .noinstr.text section
Date: Fri, 15 Apr 2022 10:37:04 +0800	[thread overview]
Message-ID: <202204151047.7ZlroG22-lkp@intel.com> (raw)

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-a006 (https://download.01.org/0day-ci/archive/20220415/202204151047.7ZlroG22-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
        # 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
        make 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_fast_syscall_32()+0x1b: .noinstr.text+0x1b: call to static_key_count.constprop.0() leaves .noinstr.text section
   vmlinux.o: warning: objtool: do_syscall_64()+0xc: .noinstr.text+0xf6: call to static_key_count.constprop.0() leaves .noinstr.text section
   vmlinux.o: warning: objtool: do_int80_syscall_32()+0x1b: .noinstr.text+0x18e: call to static_key_count.constprop.0() leaves .noinstr.text section
   vmlinux.o: warning: objtool: enter_from_user_mode()+0x18: .noinstr.text+0x30b8: call to __kcsan_check_access() leaves .noinstr.text section
   vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x1d: .noinstr.text+0x31d2: call to __kcsan_check_access() leaves .noinstr.text section
   vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x18: .noinstr.text+0x3313: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: exit_to_user_mode()+0x10: .noinstr.text+0x3425: call to static_key_count.constprop.0() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: syscall_exit_to_user_mode()+0x29: .noinstr.text+0x346a: call to static_key_count.constprop.0() leaves .noinstr.text section
   vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x18: .noinstr.text+0x349e: call to __kcsan_check_access() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: irqentry_exit_to_user_mode()+0x17: .noinstr.text+0x35fb: call to static_key_count.constprop.0() leaves .noinstr.text section

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

                 reply	other threads:[~2022-04-15  2:37 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=202204151047.7ZlroG22-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jpoimboe@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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®