public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Julien Thierry <jthierry@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: jpoimboe@redhat.com, peterz@infradead.org, mhelsley@vmware.com,
	mbenes@suse.cz, Julien Thierry <jthierry@redhat.com>
Subject: [PATCH v2 3/4] objtool: orc: Skip setting orc_entry for non-text sections
Date: Mon,  8 Jun 2020 08:12:02 +0100	[thread overview]
Message-ID: <20200608071203.4055-4-jthierry@redhat.com> (raw)
In-Reply-To: <20200608071203.4055-1-jthierry@redhat.com>

Orc generation is only done for text sections, but some instructions
can be found in non-text sections (e.g. .discard.text sections).

Skip setting their orc sections since their whole sections will be
skipped for orc generation.

Signed-off-by: Julien Thierry <jthierry@redhat.com>
---
 tools/objtool/orc_gen.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tools/objtool/orc_gen.c b/tools/objtool/orc_gen.c
index c9549988121a..e74578640705 100644
--- a/tools/objtool/orc_gen.c
+++ b/tools/objtool/orc_gen.c
@@ -18,6 +18,9 @@ int create_orc(struct objtool_file *file)
 		struct cfi_reg *cfa = &insn->cfi.cfa;
 		struct cfi_reg *bp = &insn->cfi.regs[CFI_BP];
 
+		if (!insn->sec->text)
+			continue;
+
 		orc->end = insn->cfi.end;
 
 		if (cfa->base == CFI_UNDEFINED) {
-- 
2.21.1


  parent reply	other threads:[~2020-06-08  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08  7:11 [PATCH v2 0/4] Remove dependency of check subcmd upon orc Julien Thierry
2020-06-08  7:12 ` [PATCH v2 1/4] objtool: Move object file loading out of check Julien Thierry
2020-06-08 18:49   ` Matt Helsley
2020-06-08  7:12 ` [PATCH v2 2/4] objtool: Move orc outside " Julien Thierry
2020-06-08 18:50   ` Matt Helsley
2020-06-08  7:12 ` Julien Thierry [this message]
2020-06-08  7:12 ` [PATCH v2 4/4] objtool: orc_gen: Move orc_entry out of instruction structure Julien Thierry
2020-06-09  9:44 ` [PATCH v2 0/4] Remove dependency of check subcmd upon orc Miroslav Benes

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=20200608071203.4055-4-jthierry@redhat.com \
    --to=jthierry@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mhelsley@vmware.com \
    --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