From: Peter Zijlstra <peterz@infradead.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, jpoimboe@kernel.org,
andrew.cooper3@citrix.com, David.Kaplan@amd.com
Subject: Re: [PATCH 2/2] x86/ibt: Avoid duplicate ENDBR in __put_user_nocheck*()
Date: Wed, 2 Aug 2023 22:33:22 +0200 [thread overview]
Message-ID: <20230802203322.GG231007@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230802110323.086971726@infradead.org>
On Wed, Aug 02, 2023 at 12:55:47PM +0200, Peter Zijlstra wrote:
> Commit cb855971d717 ("x86/putuser: Provide room for padding") changed
> __put_user_nocheck_*() into proper functions but failed to note that
> SYM_FUNC_START() already provides ENDBR, rendering the explicit ENDBR
> superfluous.
The below objtool thing reliably detects this pattern:
vmlinux.o: warning: objtool: __put_user_nocheck_1+0x4: duplicate ENDBR
vmlinux.o: warning: objtool: __put_user_nocheck_2+0x4: duplicate ENDBR
vmlinux.o: warning: objtool: __put_user_nocheck_4+0x4: duplicate ENDBR
vmlinux.o: warning: objtool: __put_user_nocheck_8+0x4: duplicate ENDBR
---
tools/objtool/check.c | 27 +++++++++++++++++++++++----
1 file changed, 23 insertions(+), 4 deletions(-)
diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index 8936a05f0e5a..c6ba6e768b03 100644
--- a/tools/objtool/check.c
+++ b/tools/objtool/check.c
@@ -4254,13 +4254,30 @@ static bool noendbr_range(struct objtool_file *file, struct instruction *insn)
return insn->offset == sym->offset + sym->len;
}
-static int validate_ibt_insn(struct objtool_file *file, struct instruction *insn)
+static int validate_ibt_insn(struct objtool_file *file,
+ struct instruction *insn,
+ struct instruction *prev)
{
struct instruction *dest;
struct reloc *reloc;
unsigned long off;
int warnings = 0;
+ if (prev && prev->sym && prev->sym == insn->sym &&
+ prev->type == INSN_ENDBR && insn->type == INSN_ENDBR) {
+ /*
+ * ___bpf_prog_run() is a maze of 'label as value' and
+ * 'computed goto' and GCC gets confused and emits back-to-back
+ * ENDBR due to failing to merge two labels.
+ *
+ * Don't warn about this until GCC is fixed or verbose.
+ */
+ if (strcmp(insn->sym->name, "___bpf_prog_run") != 0 || opts.verbose) {
+ WARN_INSN(insn, "duplicate ENDBR");
+ warnings++;
+ }
+ }
+
/*
* Looking for function pointer load relocations. Ignore
* direct/indirect branches:
@@ -4382,11 +4399,13 @@ static int validate_ibt(struct objtool_file *file)
{
struct section *sec;
struct reloc *reloc;
- struct instruction *insn;
+ struct instruction *insn, *prev = NULL;
int warnings = 0;
- for_each_insn(file, insn)
- warnings += validate_ibt_insn(file, insn);
+ for_each_insn(file, insn) {
+ warnings += validate_ibt_insn(file, insn, prev);
+ prev = insn;
+ }
for_each_sec(file, sec) {
next prev parent reply other threads:[~2023-08-02 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 10:55 [PATCH 0/2] x86/ibt: Fix some spurious ENDBR instances Peter Zijlstra
2023-08-02 10:55 ` [PATCH 1/2] x86/ibt: Suppress spurious ENDBR Peter Zijlstra
2023-09-12 11:08 ` [tip: x86/urgent] " tip-bot2 for Peter Zijlstra
2023-09-12 15:54 ` tip-bot2 for Peter Zijlstra
2023-08-02 10:55 ` [PATCH 2/2] x86/ibt: Avoid duplicate ENDBR in __put_user_nocheck*() Peter Zijlstra
2023-08-02 20:33 ` Peter Zijlstra [this message]
2023-09-12 11:08 ` [tip: x86/urgent] " tip-bot2 for Peter Zijlstra
2023-09-12 15:54 ` tip-bot2 for Peter Zijlstra
2023-08-02 11:25 ` [PATCH 0/2] x86/ibt: Fix some spurious ENDBR instances andrew.cooper3
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=20230802203322.GG231007@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=David.Kaplan@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®