mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [tip:locking/core 1/2] vmlinux.o: warning: objtool: mce_start()+0x69: call to ftrace_likely_update() leaves .noinstr.text section
@ 2022-02-14  3:18 kernel test robot
  2022-02-14  3:20 ` Randy Dunlap
  0 siblings, 1 reply; 2+ messages in thread
From: kernel test robot @ 2022-02-14  3:18 UTC (permalink / raw)
  To: Borislav Petkov; +Cc: kbuild-all, linux-kernel, x86

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
head:   b008893b08dcc8c30d756db05c229a1491bcb992
commit: f5c54f77b07b278cfde4a654e111c39996ac8b5b [1/2] cpumask: Add a x86-specific cpumask_clear_cpu() helper
config: x86_64-randconfig-c002-20220214 (https://download.01.org/0day-ci/archive/20220214/202202141123.gFaMRI4k-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/tip/tip.git/commit/?id=f5c54f77b07b278cfde4a654e111c39996ac8b5b
        git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
        git fetch --no-tags tip locking/core
        git checkout f5c54f77b07b278cfde4a654e111c39996ac8b5b
        # 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: __rdgsbase_inactive()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: __wrgsbase_inactive()+0x39: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: fixup_bad_iret()+0x72: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: noist_exc_debug()+0x39: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: exc_nmi()+0x31: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: poke_int3_handler()+0x47: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: mce_check_crashing_cpu()+0x2c: call to ftrace_likely_update() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: mce_start()+0x69: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: mce_read_aux()+0x41: call to mca_msr_reg() leaves .noinstr.text section
   vmlinux.o: warning: objtool: do_machine_check()+0x49: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: exc_machine_check()+0x4f: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: rcu_dynticks_eqs_enter()+0x1a: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: rcu_dynticks_eqs_exit()+0x1a: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: rcu_eqs_exit.constprop.0()+0x37: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: rcu_eqs_enter.constprop.0()+0x3c: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: rcu_irq_exit()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: rcu_nmi_enter()+0x2e: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: rcu_irq_enter()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: irqentry_nmi_enter()+0x48: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: irqentry_nmi_exit()+0x73: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: enter_from_user_mode()+0x58: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x5e: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x58: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x58: call to ftrace_likely_update() leaves .noinstr.text section
   vmlinux.o: warning: objtool: irqentry_exit()+0x3c: call to ftrace_likely_update() leaves .noinstr.text section

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [tip:locking/core 1/2] vmlinux.o: warning: objtool: mce_start()+0x69: call to ftrace_likely_update() leaves .noinstr.text section
  2022-02-14  3:18 [tip:locking/core 1/2] vmlinux.o: warning: objtool: mce_start()+0x69: call to ftrace_likely_update() leaves .noinstr.text section kernel test robot
@ 2022-02-14  3:20 ` Randy Dunlap
  0 siblings, 0 replies; 2+ messages in thread
From: Randy Dunlap @ 2022-02-14  3:20 UTC (permalink / raw)
  To: kernel test robot, Borislav Petkov
  Cc: kbuild-all, linux-kernel, x86, Peter Zijlstra



On 2/13/22 19:18, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> head:   b008893b08dcc8c30d756db05c229a1491bcb992
> commit: f5c54f77b07b278cfde4a654e111c39996ac8b5b [1/2] cpumask: Add a x86-specific cpumask_clear_cpu() helper
> config: x86_64-randconfig-c002-20220214 (https://download.01.org/0day-ci/archive/20220214/202202141123.gFaMRI4k-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/tip/tip.git/commit/?id=f5c54f77b07b278cfde4a654e111c39996ac8b5b
>         git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>         git fetch --no-tags tip locking/core
>         git checkout f5c54f77b07b278cfde4a654e111c39996ac8b5b
>         # 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: __rdgsbase_inactive()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: __wrgsbase_inactive()+0x39: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: fixup_bad_iret()+0x72: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: noist_exc_debug()+0x39: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: exc_nmi()+0x31: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: poke_int3_handler()+0x47: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: mce_check_crashing_cpu()+0x2c: call to ftrace_likely_update() leaves .noinstr.text section
>>> vmlinux.o: warning: objtool: mce_start()+0x69: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: mce_read_aux()+0x41: call to mca_msr_reg() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: do_machine_check()+0x49: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: exc_machine_check()+0x4f: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: rcu_dynticks_eqs_enter()+0x1a: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: rcu_dynticks_eqs_exit()+0x1a: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: rcu_eqs_exit.constprop.0()+0x37: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: rcu_eqs_enter.constprop.0()+0x3c: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: rcu_irq_exit()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: rcu_nmi_enter()+0x2e: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: rcu_irq_enter()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: irqentry_nmi_enter()+0x48: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: irqentry_nmi_exit()+0x73: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: enter_from_user_mode()+0x58: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x5e: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x58: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x58: call to ftrace_likely_update() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: irqentry_exit()+0x3c: call to ftrace_likely_update() leaves .noinstr.text section

Yes. See Peter's response here:
  https://lore.kernel.org/all/YgdqmbK7Irwa2Ryh@hirez.programming.kicks-ass.net/

-- 
~Randy

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-02-14  3:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-14  3:18 [tip:locking/core 1/2] vmlinux.o: warning: objtool: mce_start()+0x69: call to ftrace_likely_update() leaves .noinstr.text section kernel test robot
2022-02-14  3:20 ` Randy Dunlap

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®