From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [stable:linux-5.10.y 3202/6129] vmlinux.o: warning: objtool: __do_fast_syscall_32()+0x98: call to trace_hardirqs_off() leaves .noinstr.text section
Date: Tue, 29 Jun 2021 13:05:09 +0800 [thread overview]
Message-ID: <202106291306.0c9aeGFw-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.y
head: 3de043c6851d7c604e0cabdf8e2aca7797952aa9
commit: e40384fcd6005bf887c5e31c6e8c408c0e55aad2 [3202/6129] x86/entry: Fix entry/exit mismatch on failed fast 32-bit syscalls
config: x86_64-buildonly-randconfig-r002-20210629 (attached as .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/stable/linux-stable.git/commit/?id=e40384fcd6005bf887c5e31c6e8c408c0e55aad2
git remote add stable https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch --no-tags stable linux-5.10.y
git checkout e40384fcd6005bf887c5e31c6e8c408c0e55aad2
# save the attached .config 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()+0x98: call to trace_hardirqs_off() leaves .noinstr.text section
vmlinux.o: warning: objtool: match_held_lock()+0x10a: call to rcu_read_lock_any_held() 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: 42903 bytes --]
next reply other threads:[~2021-06-29 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 5:05 kernel test robot [this message]
2021-07-08 13:37 ` [PATCH] x86/entry: Fix noinstr violation Thomas Gleixner
2021-07-08 18:37 ` Thomas Gleixner
2021-07-08 18:37 ` Thomas Gleixner
2021-07-08 19:02 ` Greg Kroah-Hartman
2021-07-08 19:02 ` Greg Kroah-Hartman
2021-07-08 19:17 ` Thomas Gleixner
2021-07-08 19:17 ` Thomas Gleixner
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=202106291306.0c9aeGFw-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.