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 5/5] arch/x86/lib/copy_user_64.o: warning: objtool: copy_user_enhanced_fast_string() falls through to next function copy_user_generic_unrolled()
Date: Tue, 12 Apr 2022 13:52:48 +0800 [thread overview]
Message-ID: <202204121317.36kQoGCk-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git objtool-run
head: 0060ff03f4882dcb7911b968e5d1f31aaf840c33
commit: 0060ff03f4882dcb7911b968e5d1f31aaf840c33 [5/5] todo
config: x86_64-randconfig-c022-20220411 (https://download.01.org/0day-ci/archive/20220412/202204121317.36kQoGCk-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=0060ff03f4882dcb7911b968e5d1f31aaf840c33
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 0060ff03f4882dcb7911b968e5d1f31aaf840c33
# 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 >>):
>> arch/x86/lib/copy_user_64.o: warning: objtool: copy_user_enhanced_fast_string() falls through to next function copy_user_generic_unrolled()
--
>> arch/x86/lib/memcpy_64.o: warning: objtool: __memcpy() falls through to next function memcpy_erms()
--
>> arch/x86/lib/memset_64.o: warning: objtool: __memset() falls through to next function memset_erms()
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-12 5:53 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=202204121317.36kQoGCk-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®