From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: Re: [PATCH] x86/retpoline,kprobes: Fix "Fix position of thunk sections with CONFIG_LTO_CLANG"
Date: Fri, 4 Aug 2023 10:28:53 +0200 [thread overview]
Message-ID: <20230804082853.GM212435@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230803230323.1478869-1-andrew.cooper3@citrix.com>
On Fri, Aug 04, 2023 at 12:03:23AM +0100, Andrew Cooper wrote:
> Lets hope there are no .text..__x86womble sections around.
>
> Fixes: 973ab2d61f33 ("x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG")
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Petr Pavlu <petr.pavlu@suse.com>
> CC: Peter Zijlstra (Intel) <peterz@infradead.org>
> CC: Josh Poimboeuf <jpoimboe@kernel.org>
> CC: linux-kernel@vger.kernel.org
>
> Alternatively,
>
> int strstarts(const char *s1, const char *s2)
> {
> return strncmp(s1, s2, strlen(s2));
> }
Durr, I hate C ;-/ And yes, we have a ton of it, lemme try that
strstarts thing.
next prev parent reply other threads:[~2023-08-04 8:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 9:19 [PATCH v2 0/2] x86/retpoline,kprobes: Fix the [__indirect_thunk_start, ..end] range Petr Pavlu
2023-07-11 9:19 ` [PATCH v2 1/2] x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG Petr Pavlu
2023-08-02 14:33 ` [tip: x86/core] " tip-bot2 for Petr Pavlu
2023-08-03 21:55 ` Josh Poimboeuf
2023-08-03 23:03 ` [PATCH] x86/retpoline,kprobes: Fix "Fix position of thunk sections with CONFIG_LTO_CLANG" Andrew Cooper
2023-08-04 8:28 ` Peter Zijlstra [this message]
2023-08-04 8:43 ` Peter Zijlstra
2023-11-10 0:36 ` Josh Poimboeuf
2023-08-14 10:00 ` [tip: x86/urgent] x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG tip-bot2 for Petr Pavlu
2023-07-11 9:19 ` [PATCH v2 2/2] x86/retpoline,kprobes: Skip optprobe check for indirect jumps with retpolines and IBT Petr Pavlu
2023-07-11 12:33 ` Masami Hiramatsu
2023-08-02 14:33 ` [tip: x86/core] " tip-bot2 for Petr Pavlu
2023-08-14 10:00 ` [tip: x86/urgent] " tip-bot2 for Petr Pavlu
2023-07-29 15:14 ` [PATCH v2 0/2] x86/retpoline,kprobes: Fix the [__indirect_thunk_start, ..end] range Masami Hiramatsu
2023-07-31 10:22 ` 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=20230804082853.GM212435@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrew.cooper3@citrix.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr.pavlu@suse.com \
/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