From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [peterz-queue:x86/wip.ibt.ud1 39/56] security/keys/process_keys.o: warning: objtool: .text: unexpected end of section
Date: Tue, 15 Mar 2022 13:20:33 +0800 [thread overview]
Message-ID: <202203151359.uzN2HcRc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/wip.ibt.ud1
head: f86aacc74625dc1b2b1d2ae309d2a832dba4d4f4
commit: 4c90d8ae1079abe5849747099a8ba128a7a19d84 [39/56] x86: Mark __invalid_creds() __noreturn
config: x86_64-buildonly-randconfig-r006-20220314 (https://download.01.org/0day-ci/archive/20220315/202203151359.uzN2HcRc-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=4c90d8ae1079abe5849747099a8ba128a7a19d84
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue x86/wip.ibt.ud1
git checkout 4c90d8ae1079abe5849747099a8ba128a7a19d84
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/misc/ fs// kernel// security/
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 >>):
>> security/keys/process_keys.o: warning: objtool: .text: unexpected end of section
--
>> security/keys/request_key_auth.o: warning: objtool: free_request_key_auth() falls through to next function request_key_auth_rcu_disposal()
--
>> drivers/misc/vmw_vmci/vmci_context.o: warning: objtool: ctx_free_ctx() falls through to next function vmci_ctx_put()
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-15 5:21 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=202203151359.uzN2HcRc-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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®