From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, baron@akamai.com, rostedt@goodmis.org,
ardb@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, christian@bricart.de,
song@kernel.org, mcgrof@kernel.org
Subject: Re: [PATCH] x86/static_call: Fix __static_call_fixup()
Date: Tue, 15 Aug 2023 17:10:32 -0700 [thread overview]
Message-ID: <20230816001032.n4jp2uek3gi654bq@treble> (raw)
In-Reply-To: <20230815230809.GA973560@hirez.programming.kicks-ass.net>
On Wed, Aug 16, 2023 at 01:08:09AM +0200, Peter Zijlstra wrote:
> bool __static_call_fixup(void *tramp, u8 op, void *dest)
> {
> + /*
> + * Not all .return_sites are a static_call trampoline (most are not).
> + * Check if the next 3 bytes are still kernel text, if not, then this
s/3/7 ?
> + * definitely is not a trampoline and we need not worry further.
> + *
> + * This avoids the memcmp() below tripping over pagefaults etc..
> + */
> + if (!kernel_text_address(tramp+7))
> + return false;
> +
> if (memcmp(tramp+5, tramp_ud, 3)) {
> /* Not a trampoline site, not our problem. */
> return false;
kernel_text_address() can be quite heavyweight to call in a loop during
module loading. Maybe that doesn't matter much. But it would be a lot
faster to only call kernel_text_address() if tramp+7 is on the next
page.
--
Josh
next prev parent reply other threads:[~2023-08-16 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 23:08 Peter Zijlstra
2023-08-15 23:14 ` Peter Zijlstra
2023-08-16 0:10 ` Josh Poimboeuf [this message]
2023-08-16 9:39 ` Peter Zijlstra
2023-08-16 0:41 ` Steven Rostedt
2023-08-16 9:39 ` Peter Zijlstra
2023-08-16 10:44 ` [PATCH v2] " Peter Zijlstra
2023-08-16 21:02 ` Josh Poimboeuf
2023-08-17 11:47 ` [tip: x86/urgent] " tip-bot2 for Peter Zijlstra
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=20230816001032.n4jp2uek3gi654bq@treble \
--to=jpoimboe@kernel.org \
--cc=ardb@kernel.org \
--cc=baron@akamai.com \
--cc=bp@alien8.de \
--cc=christian@bricart.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--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®