From: Kees Cook <keescook@chromium.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH] lkdtm: Avoid objtool/ibt warning
Date: Wed, 16 Nov 2022 14:31:49 -0800 [thread overview]
Message-ID: <202211161431.FF6F3BB867@keescook> (raw)
In-Reply-To: <Y3JdgbXRV0MNZ+9h@hirez.programming.kicks-ass.net>
On Mon, Nov 14, 2022 at 04:23:45PM +0100, Peter Zijlstra wrote:
> On Mon, Nov 14, 2022 at 08:26:17PM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 094226ad94f471a9f19e8f8e7140a09c2625abaa
> > commit: 656d054e0a15ec327bd82801ccd58201e59f6896 jump_label,noinstr: Avoid instrumentation for JUMP_LABEL=n builds
> > date: 6 months ago
> > config: x86_64-buildonly-randconfig-r001-20221114
> > compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> > reproduce (this is a W=1 build):
> > # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=656d054e0a15ec327bd82801ccd58201e59f6896
> > git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > git fetch --no-tags linus master
> > git checkout 656d054e0a15ec327bd82801ccd58201e59f6896
> > # save the config file
> > mkdir build_dir && cp config build_dir/.config
> > make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>
>
> > >> vmlinux.o: warning: objtool: lkdtm_UNSET_SMEP+0x1c3: relocation to !ENDBR: native_write_cr4+0x41
>
> ---
> Subject: lkdtm: Avoid objtool/ibt warning
> From: Peter Zijlstra <peterz@infradead.org>
> Date: Mon Nov 14 16:17:50 CET 2022
>
> For certain configs objtool will complain like:
>
> vmlinux.o: warning: objtool: lkdtm_UNSET_SMEP+0x1c3: relocation to !ENDBR: native_write_cr4+0x41
>
> What happens is that GCC optimizes the loop:
>
> insn = (unsigned char *)native_write_cr4;
> for (i = 0; i < MOV_CR4_DEPTH; i++)
>
> to read something like:
>
> for (insn = (unsigned char *)native_write_cr4;
> insn < (unsigned char *)native_write_cr4 + MOV_CR4_DEPTH;
> insn++)
>
> Which then obviously generates the text reference
> native_write_cr4+041. Since none of this is a fast path, simply
> confuse GCC enough to inhibit this optimization.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Kees Cook <keescook@chromium.org>
Please feel free to carry this, or forward it to Greg KH.
-Kees
> ---
> drivers/misc/lkdtm/bugs.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/drivers/misc/lkdtm/bugs.c
> +++ b/drivers/misc/lkdtm/bugs.c
> @@ -487,6 +487,7 @@ static void lkdtm_UNSET_SMEP(void)
> * the cr4 writing instruction.
> */
> insn = (unsigned char *)native_write_cr4;
> + OPTIMIZER_HIDE_VAR(insn);
> for (i = 0; i < MOV_CR4_DEPTH; i++) {
> /* mov %rdi, %cr4 */
> if (insn[i] == 0x0f && insn[i+1] == 0x22 && insn[i+2] == 0xe7)
--
Kees Cook
next prev parent reply other threads:[~2022-11-16 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 12:26 vmlinux.o: warning: objtool: lkdtm_UNSET_SMEP+0x1c3: relocation to !ENDBR: native_write_cr4+0x41 kernel test robot
2022-11-14 15:23 ` [PATCH] lkdtm: Avoid objtool/ibt warning Peter Zijlstra
2022-11-16 22:31 ` Kees Cook [this message]
2023-06-09 7:47 ` [tip: objtool/core] " tip-bot2 for Peter Zijlstra
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=202211161431.FF6F3BB867@keescook \
--to=keescook@chromium.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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