From: kbuild test robot <fengguang.wu@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
James Morris <james.l.morris@oracle.com>,
Jann Horn <jann@thejh.net>
Subject: security/yama/yama_lsm.o: warning: objtool: report_access()+0x210: function has unreachable instruction
Date: Tue, 19 Jul 2016 22:20:05 +0800 [thread overview]
Message-ID: <201607192204.fvKwcnpe%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 47ef4ad2684d380dd6d596140fb79395115c3950
commit: dca6b4149181baaa363b9a7ce7c550840bb3bc83 Yama: fix double-spinlock and user access in atomic context
date: 8 weeks ago
config: x86_64-randconfig-s2-07191718 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout dca6b4149181baaa363b9a7ce7c550840bb3bc83
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> security/yama/yama_lsm.o: warning: objtool: report_access()+0x210: function has unreachable instruction
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 22748 bytes --]
next reply other threads:[~2016-07-19 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 14:20 kbuild test robot [this message]
2016-07-20 1:12 ` [kbuild-all] security/yama/yama_lsm.o: warning: objtool: report_access()+0x210: function has unreachable instruction Fengguang Wu
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=201607192204.fvKwcnpe%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=james.l.morris@oracle.com \
--cc=jann@thejh.net \
--cc=kbuild-all@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 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.