From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Miroslav Benes <mbenes@suse.cz>
Subject: Re: [PATCH 1/3] objtool: Separate prefix code from stack validation code
Date: Thu, 13 Apr 2023 11:30:31 +0200 [thread overview]
Message-ID: <20230413093031.GK4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <d7f31ac2de462d0cd7b1db01b7ecb525c057c8f6.1681331135.git.jpoimboe@kernel.org>
On Wed, Apr 12, 2023 at 01:26:13PM -0700, Josh Poimboeuf wrote:
> Simplify the prefix code and make it a standalone feature.
The main thing being that you moved it all after
validate_reachable_instructions() ?
> +static int add_prefix_symbols(struct objtool_file *file)
> +{
> + struct section *sec;
> + struct symbol *func;
> + int ret, warnings = 0;
> +
> + for_each_sec(file, sec) {
> + if (!(sec->sh.sh_flags & SHF_EXECINSTR))
> + continue;
> +
> + list_for_each_entry(func, &sec->symbol_list, list) {
One of the other patches did a sec_for_each_symbol() thing.
> + if (func->type != STT_FUNC)
> + continue;
> +
> + add_prefix_symbol(file, func);
> + }
> + }
> +
> + return warnings;
> +}
next prev parent reply other threads:[~2023-04-13 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 20:26 [PATCH 0/3] objtool: Generate ORC data for __pfx code Josh Poimboeuf
2023-04-12 20:26 ` [PATCH 1/3] objtool: Separate prefix code from stack validation code Josh Poimboeuf
2023-04-13 9:30 ` Peter Zijlstra [this message]
2023-04-13 15:27 ` Josh Poimboeuf
2023-04-14 14:47 ` [tip: objtool/core] " tip-bot2 for Josh Poimboeuf
2023-04-12 20:26 ` [PATCH 2/3] x86/linkage: Fix padding for typed functions Josh Poimboeuf
2023-04-14 14:47 ` [tip: objtool/core] " tip-bot2 for Josh Poimboeuf
2023-04-12 20:26 ` [PATCH 3/3] objtool: Generate ORC data for __pfx code Josh Poimboeuf
2023-04-13 11:23 ` Peter Zijlstra
2023-04-13 11:24 ` Peter Zijlstra
2023-04-13 15:29 ` Josh Poimboeuf
2023-04-13 19:24 ` Peter Zijlstra
2023-04-13 19:30 ` Josh Poimboeuf
2023-04-14 14:47 ` [tip: objtool/core] " tip-bot2 for 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=20230413093031.GK4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--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®