From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [sashal-stable:pending-5.13 169/349] vmlinux.o: warning: objtool: rcu_dynticks_eqs_enter()+0x18: call to rcu_dynticks_task_trace_enter() leaves .noinstr.text section
Date: Fri, 17 Sep 2021 16:26:20 +0800 [thread overview]
Message-ID: <202109171613.ocPfH6Ac-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4090 bytes --]
TO: Sasha Levin <sashal@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git pending-5.13
head: a2d3e0d9335a9de04e9441bc1766f0fd601a49af
commit: 932725ab57b133552b8420477a59a60513f29673 [169/349] rcu: Fix macro name CONFIG_TASKS_RCU_TRACE
config: x86_64-buildonly-randconfig-r001-20210916 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c8b3d7d6d6de37af68b2f379d0e37304f78e115f)
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/sashal/linux-stable.git/commit/?id=932725ab57b133552b8420477a59a60513f29673
git remote add sashal-stable https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
git fetch --no-tags sashal-stable pending-5.13
git checkout 932725ab57b133552b8420477a59a60513f29673
# save the attached .config 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()+0x109: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: fixup_bad_iret()+0x32: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: noist_exc_debug()+0x4e: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: exc_nmi()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: poke_int3_handler()+0x4e: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __sev_es_ist_exit()+0x31: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __sev_get_ghcb()+0x49: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __sev_put_ghcb()+0x4b: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: kernel_exc_vmm_communication()+0x54: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: rcu_eqs_enter()+0x42: call to ftrace_likely_update() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: rcu_dynticks_eqs_enter()+0x18: call to rcu_dynticks_task_trace_enter() leaves .noinstr.text section
vmlinux.o: warning: objtool: rcu_eqs_exit()+0x36: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: rcu_nmi_enter()+0x3f: call to ftrace_likely_update() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: rcu_dynticks_eqs_exit()+0x29: call to rcu_dynticks_task_trace_exit() leaves .noinstr.text section
vmlinux.o: warning: objtool: enter_from_user_mode()+0x31: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x3b: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x31: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x31: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_nmi_enter()+0x38: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_nmi_exit()+0x2b: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __context_tracking_enter()+0x2f: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: context_tracking_recursion_enter()+0x41: 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
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 36440 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [sashal-stable:pending-5.13 169/349] vmlinux.o: warning: objtool: rcu_dynticks_eqs_enter()+0x18: call to rcu_dynticks_task_trace_enter() leaves .noinstr.text section
Date: Fri, 17 Sep 2021 16:26:20 +0800 [thread overview]
Message-ID: <202109171613.ocPfH6Ac-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4141 bytes --]
TO: Sasha Levin <sashal@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git pending-5.13
head: a2d3e0d9335a9de04e9441bc1766f0fd601a49af
commit: 932725ab57b133552b8420477a59a60513f29673 [169/349] rcu: Fix macro name CONFIG_TASKS_RCU_TRACE
config: x86_64-buildonly-randconfig-r001-20210916 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c8b3d7d6d6de37af68b2f379d0e37304f78e115f)
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/sashal/linux-stable.git/commit/?id=932725ab57b133552b8420477a59a60513f29673
git remote add sashal-stable https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
git fetch --no-tags sashal-stable pending-5.13
git checkout 932725ab57b133552b8420477a59a60513f29673
# save the attached .config 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()+0x109: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: fixup_bad_iret()+0x32: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: noist_exc_debug()+0x4e: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: exc_nmi()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: poke_int3_handler()+0x4e: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __sev_es_ist_exit()+0x31: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __sev_get_ghcb()+0x49: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __sev_put_ghcb()+0x4b: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: kernel_exc_vmm_communication()+0x54: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: rcu_eqs_enter()+0x42: call to ftrace_likely_update() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: rcu_dynticks_eqs_enter()+0x18: call to rcu_dynticks_task_trace_enter() leaves .noinstr.text section
vmlinux.o: warning: objtool: rcu_eqs_exit()+0x36: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: rcu_nmi_enter()+0x3f: call to ftrace_likely_update() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: rcu_dynticks_eqs_exit()+0x29: call to rcu_dynticks_task_trace_exit() leaves .noinstr.text section
vmlinux.o: warning: objtool: enter_from_user_mode()+0x31: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x3b: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x31: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x31: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_nmi_enter()+0x38: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_nmi_exit()+0x2b: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: __context_tracking_enter()+0x2f: call to ftrace_likely_update() leaves .noinstr.text section
vmlinux.o: warning: objtool: context_tracking_recursion_enter()+0x41: 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(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 36440 bytes --]
next reply other threads:[~2021-09-17 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 8:26 kernel test robot [this message]
2021-09-17 8:26 ` [sashal-stable:pending-5.13 169/349] vmlinux.o: warning: objtool: rcu_dynticks_eqs_enter()+0x18: call to rcu_dynticks_task_trace_enter() leaves .noinstr.text section 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=202109171613.ocPfH6Ac-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.