From: "Jürgen Groß" <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org
Subject: Re: [tip: x86/core] x86/alternative: Patch a single alternative location only once
Date: Tue, 14 Oct 2025 16:08:47 +0200 [thread overview]
Message-ID: <4fd058ac-3af5-4778-842c-9a185d828c9d@suse.com> (raw)
In-Reply-To: <20251014125909.GAaO5JHU_cgsPgstc_@fat_crate.local>
[-- Attachment #1.1.1: Type: text/plain, Size: 1706 bytes --]
On 14.10.25 14:59, Borislav Petkov wrote:
> On Tue, Oct 14, 2025 at 08:42:34AM -0000, tip-bot2 for Juergen Gross wrote:
>> @@ -648,6 +648,8 @@ void __init_or_module noinline apply_alternatives(struct alt_instr *start,
>> u8 insn_buff[MAX_PATCH_LEN];
>> u8 *instr;
>> struct alt_instr *a, *b;
>> + unsigned int instances = 0;
>> + bool patched = false;
>
> Except that we have the reverse fir tree rule in tip for function-local vars.
Okay.
>> @@ -692,14 +698,19 @@ void __init_or_module noinline apply_alternatives(struct alt_instr *start,
>> * - feature not present but ALT_FLAG_NOT is set to mean,
>> * patch if feature is *NOT* present.
>> */
>> - if (!boot_cpu_has(a->cpuid) == !(a->flags & ALT_FLAG_NOT)) {
>> - memcpy(insn_buff, instr, a->instrlen);
>> - optimize_nops(instr, insn_buff, a->instrlen);
>> - } else {
>> + if (!boot_cpu_has(a->cpuid) != !(a->flags & ALT_FLAG_NOT)) {
>> apply_one_alternative(instr, insn_buff, a);
>> + patched = true;
>> }
>>
>> - text_poke_early(instr, insn_buff, a->instrlen);
>> + instances--;
>> + if (!instances) {
>> + if (!patched) {
>
> I don't see how this is making this code better - this is slowly turning into
> an unreadable mess with those magic "instances" and "patched".
>
> And frankly, the justification for this patch is also meh: an interrupt might
> use the location?!? If this is a real issue then we better disable IRQs around
> it. But not make the code yucky.
For one it is not the only justification.
And just for the record: NMI handling is using ALTERNATIVE_2, so you
can't just "disable interrupts" and be sure it will work.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-10-14 14:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 11:29 [PATCH 0/3] x86/alternative: Make alternative patching more robust Juergen Gross
2025-09-29 11:29 ` [PATCH 1/3] x86/alternative: Drop not needed test after call of alt_replace_call() Juergen Gross
2025-10-14 8:42 ` [tip: x86/core] " tip-bot2 for Juergen Gross
2025-09-29 11:29 ` [PATCH 2/3] x86/alternative: Refactor apply_alternatives() Juergen Gross
2025-10-14 8:42 ` [tip: x86/core] " tip-bot2 for Juergen Gross
2025-09-29 11:29 ` [PATCH 3/3] x86/alternative: Patch a single alternative location only once Juergen Gross
2025-09-30 7:26 ` Peter Zijlstra
2025-09-30 7:33 ` Jürgen Groß
2025-09-30 7:39 ` Peter Zijlstra
2025-09-30 8:04 ` Jürgen Groß
2025-10-14 8:42 ` [tip: x86/core] " tip-bot2 for Juergen Gross
2025-10-14 12:59 ` Borislav Petkov
2025-10-14 13:25 ` Borislav Petkov
2025-10-14 14:13 ` Jürgen Groß
2025-10-14 14:17 ` Borislav Petkov
2025-10-14 14:18 ` Peter Zijlstra
2025-10-14 14:26 ` Juergen Gross
2025-10-14 14:29 ` Borislav Petkov
2025-10-14 14:08 ` Jürgen Groß [this message]
2025-10-14 14:12 ` Borislav Petkov
2025-10-14 14:22 ` Jürgen Groß
2025-10-14 14:26 ` Borislav Petkov
2025-10-14 14:31 ` Jürgen Groß
2025-10-14 14:39 ` Borislav Petkov
2025-10-14 14:46 ` Jürgen Groß
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=4fd058ac-3af5-4778-842c-9a185d828c9d@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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®