From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [ammarfaizi2-block:paulmck/linux-rcu/dev.2022.06.15c 12/12] vmlinux.o: warning: objtool: __ct_user_enter+0x75: call to __kasan_check_write() leaves .noinstr.text section
Date: Tue, 21 Jun 2022 04:08:03 +0800 [thread overview]
Message-ID: <202206210326.jhkcWRkx-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: "GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
CC: linux-kernel@vger.kernel.org
TO: "Paul E. McKenney" <paulmck@kernel.org>
CC: Marco Elver <elver@google.com>
tree: https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/dev.2022.06.15c
head: 39a7b06a0b5a00fc57b117d6abebf2d8dae21517
commit: 39a7b06a0b5a00fc57b117d6abebf2d8dae21517 [12/12] context_tracking: Use arch_atomic_read() in __ct_state for KASAN
config: x86_64-randconfig-r012-20220620 (https://download.01.org/0day-ci/archive/20220621/202206210326.jhkcWRkx-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project af6d2a0b6825e71965f3e2701a63c239fa0ad70f)
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://github.com/ammarfaizi2/linux-block/commit/39a7b06a0b5a00fc57b117d6abebf2d8dae21517
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/dev.2022.06.15c
git checkout 39a7b06a0b5a00fc57b117d6abebf2d8dae21517
# save the config file
mkdir build_dir && cp config build_dir/.config
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 where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
vmlinux.o: warning: objtool: balance_leaf+0xe882: stack state mismatch: cfa1=4+400 cfa2=4+416
vmlinux.o: warning: objtool: leaf_move_items+0xf8e: stack state mismatch: cfa1=4+160 cfa2=4+152
vmlinux.o: warning: objtool: leaf_copy_boundary_item+0x3239: stack state mismatch: cfa1=4+240 cfa2=4+232
vmlinux.o: warning: objtool: leaf_copy_items_entirely+0xd1d: stack state mismatch: cfa1=4+256 cfa2=4+248
vmlinux.o: warning: objtool: balance_internal+0x5991: stack state mismatch: cfa1=4+312 cfa2=4+320
vmlinux.o: warning: objtool: internal_move_pointers_items+0x7a0: stack state mismatch: cfa1=4+216 cfa2=4+208
vmlinux.o: warning: objtool: sync_regs+0x23: call to memcpy() leaves .noinstr.text section
vmlinux.o: warning: objtool: fixup_bad_iret+0x25: call to memset() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: __ct_user_enter+0x75: call to __kasan_check_write() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: __ct_user_exit+0x4a: call to __kasan_check_write() leaves .noinstr.text section
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-20 20:08 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=202206210326.jhkcWRkx-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox