From: Alexey Dobriyan <adobriyan@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: [tip:x86/pti 14/14] arch/x86/mm/mem_encrypt_boot.o: warning: objtool: .text+0x51: unreachable instruction
Date: Tue, 15 May 2018 01:08:52 +0300 [thread overview]
Message-ID: <20180514220852.GA8281@avx2> (raw)
In-Reply-To: <201805142145.FPNj1BCK%fengguang.wu@intel.com>
On Mon, May 14, 2018 at 09:44:48PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti
> head: 51bad67ffbce0aaa44579f84ef5d05597054ec6a
> commit: 51bad67ffbce0aaa44579f84ef5d05597054ec6a [14/14] x86/asm: Pad assembly functions with INT3 instructions
> config: x86_64-randconfig-x018-201819 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> git checkout 51bad67ffbce0aaa44579f84ef5d05597054ec6a
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All warnings (new ones prefixed by >>):
>
> >> arch/x86/mm/mem_encrypt_boot.o: warning: objtool: .text+0x51: unreachable instruction
> >> arch/x86/xen/xen-asm.o: warning: objtool: .text+0x1a: unreachable instruction
There are warnings:
arch/x86/lib/clear_page_64.o: warning: objtool: .text+0xb: unreachable instruction
0000000000000000 <clear_page_rep>:
0: b9 00 02 00 00 mov ecx,0x200
5: 31 c0 xor eax,eax
7: f3 48 ab rep stos QWORD PTR es:[rdi],rax
a: c3 ret
===> b: cc int3
c: cc int3
d: cc int3
e: cc int3
f: cc int3
0000000000000010 <clear_page_orig>:
But both function are annotated with ENTRY/ENDPROC.
prev parent reply other threads:[~2018-05-14 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 13:44 [tip:x86/pti 14/14] arch/x86/mm/mem_encrypt_boot.o: warning: objtool: .text+0x51: unreachable instruction kbuild test robot
2018-05-14 22:08 ` Alexey Dobriyan [this message]
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=20180514220852.GA8281@avx2 \
--to=adobriyan@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=tipbuild@zytor.com \
/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;
as well as URLs for NNTP newsgroup(s).