From: Kees Cook <keescook@chromium.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Miroslav Benes <mbenes@suse.cz>,
Julien Thierry <jthierry@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 1/5] objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings
Date: Thu, 2 Apr 2020 00:30:38 -0700 [thread overview]
Message-ID: <202004020030.209A886D3C@keescook> (raw)
In-Reply-To: <6653ad73c6b59c049211bd7c11ed3809c20ee9f5.1585761021.git.jpoimboe@redhat.com>
On Wed, Apr 01, 2020 at 01:23:25PM -0500, Josh Poimboeuf wrote:
> CONFIG_UBSAN_TRAP causes GCC to emit a UD2 whenever it encounters an
> unreachable code path. This includes __builtin_unreachable(). Because
> the BUG() macro uses __builtin_unreachable() after it emits its own UD2,
> this results in a double UD2. In this case objtool rightfully detects
> that the second UD2 is unreachable:
>
> init/main.o: warning: objtool: repair_env_string()+0x1c8: unreachable instruction
>
> We weren't able to figure out a way to get rid of the double UD2s, so
> just silence the warning.
>
> Cc: Kees Cook <keescook@chromium.org>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Thanks for finding a way to work around this!
Reviewed-by: Kees Cook <keescook@chromium.org>
-Kees
> ---
> tools/objtool/check.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/tools/objtool/check.c b/tools/objtool/check.c
> index e3bb76358148..aaec5e1277ea 100644
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@ -2382,14 +2382,27 @@ static bool ignore_unreachable_insn(struct instruction *insn)
> !strcmp(insn->sec->name, ".altinstr_aux"))
> return true;
>
> + if (!insn->func)
> + return false;
> +
> + /*
> + * CONFIG_UBSAN_TRAP inserts a UD2 when it sees
> + * __builtin_unreachable(). The BUG() macro has an unreachable() after
> + * the UD2, which causes GCC's undefined trap logic to emit another UD2
> + * (or occasionally a JMP to UD2).
> + */
> + if (list_prev_entry(insn, list)->dead_end &&
> + (insn->type == INSN_BUG ||
> + (insn->type == INSN_JUMP_UNCONDITIONAL &&
> + insn->jump_dest && insn->jump_dest->type == INSN_BUG)))
> + return true;
> +
> /*
> * Check if this (or a subsequent) instruction is related to
> * CONFIG_UBSAN or CONFIG_KASAN.
> *
> * End the search at 5 instructions to avoid going into the weeds.
> */
> - if (!insn->func)
> - return false;
> for (i = 0; i < 5; i++) {
>
> if (is_kasan_insn(insn) || is_ubsan_insn(insn))
> --
> 2.21.1
>
--
Kees Cook
next prev parent reply other threads:[~2020-04-02 7:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 18:23 [PATCH 0/5] objtool fixes Josh Poimboeuf
2020-04-01 18:23 ` [PATCH 1/5] objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings Josh Poimboeuf
2020-04-02 7:30 ` Kees Cook [this message]
2020-04-14 10:34 ` [tip: x86/urgent] " tip-bot2 for Josh Poimboeuf
2020-04-01 18:23 ` [PATCH 2/5] objtool: Support Clang non-section symbols in ORC dump Josh Poimboeuf
2020-04-14 10:34 ` [tip: x86/urgent] " tip-bot2 for Josh Poimboeuf
2020-04-01 18:23 ` [PATCH 3/5] objtool: Support Clang non-section symbols in ORC generation Josh Poimboeuf
2020-04-01 18:49 ` Peter Zijlstra
2020-04-01 19:05 ` Josh Poimboeuf
2020-04-01 19:08 ` Josh Poimboeuf
2020-04-03 8:58 ` Miroslav Benes
2020-04-03 14:58 ` Josh Poimboeuf
2020-04-14 10:34 ` [tip: x86/urgent] " tip-bot2 for Josh Poimboeuf
2020-04-01 18:23 ` [PATCH 4/5] objtool: Fix switch table detection in .text.unlikely Josh Poimboeuf
2020-04-14 10:34 ` [tip: x86/urgent] " tip-bot2 for Josh Poimboeuf
2020-04-01 18:23 ` [PATCH 5/5] objtool: Make BP scratch register warning more robust Josh Poimboeuf
2020-04-14 10:34 ` [tip: x86/urgent] " tip-bot2 for Josh Poimboeuf
2020-04-02 14:28 ` [PATCH 0/5] objtool fixes Peter Zijlstra
2020-04-03 9:00 ` Miroslav Benes
2020-04-09 13:53 ` Josh Poimboeuf
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=202004020030.209A886D3C@keescook \
--to=keescook@chromium.org \
--cc=jpoimboe@redhat.com \
--cc=jthierry@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=x86@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