From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Julien Thierry <jthierry@redhat.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Dmitry Golovin <dima@golovin.in>,
Nathan Chancellor <natechancellor@gmail.com>
Subject: Re: [PATCH 3/5] objtool: Support Clang non-section symbols in ORC generation
Date: Fri, 3 Apr 2020 09:58:12 -0500 [thread overview]
Message-ID: <20200403145812.zdoxkyjhn42veu52@treble> (raw)
In-Reply-To: <alpine.LSU.2.21.2004031057320.25955@pobox.suse.cz>
On Fri, Apr 03, 2020 at 10:58:20AM +0200, Miroslav Benes wrote:
> > + if (insn_sec->sym) {
> > + rela->sym = insn_sec->sym;
> > + rela->addend = insn_off;
> > + } else {
> > + /*
> > + * The Clang assembler doesn't produce section symbols, so we
> > + * have to reference the function symbol instead:
> > + */
> > + rela->sym = find_symbol_containing(insn_sec, insn_off);
> > + if (!rela->sym) {
> > + /*
> > + * Hack alert. This happens when we need to reference
> > + * the NOP pad insn immediately after the function.
> > + */
> > + rela->sym = find_symbol_containing(insn_sec,
> > + insn_off - 1);
> > + }
>
> I suppose there is always just one NOP pad insn, right? Anyway, it would
> be better to get rid of it as you proposed.
There can actually be multiple NOPs because functions are aligned on a
16-byte boundary. But the undefined ORC entry is always at the first
NOP because objtool merges duplicate entries.
--
Josh
next prev parent reply other threads:[~2020-04-03 14:58 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
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 [this message]
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=20200403145812.zdoxkyjhn42veu52@treble \
--to=jpoimboe@redhat.com \
--cc=dima@golovin.in \
--cc=jthierry@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=peterz@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
all inboxes | Powered by JetHome®