From: Will Deacon <will@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: fanqincui <fanqincui@163.com>,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Fanqin Cui <cuifq1@chinatelecom.cn>,
hanht2@chinatelecom.cn
Subject: Re: [PATCH] arm64/module: Support for patching modules during runtime
Date: Mon, 11 Aug 2025 13:05:06 +0100 [thread overview]
Message-ID: <aJnccgC5E-ui2Oqo@willie-the-truck> (raw)
In-Reply-To: <86zfc68exk.wl-maz@kernel.org>
On Mon, Aug 11, 2025 at 09:01:43AM +0100, Marc Zyngier wrote:
> On Mon, 11 Aug 2025 08:37:32 +0100,
> fanqincui <fanqincui@163.com> wrote:
> >
> > Hi will,
> > Yes, you are right. The alternative callback function lives inside the module.
> > This callback function is actually similar to kvm_update_va_mask in KVM;
> >
> > The module's callback function calculates some values based on
> > the current CPU features and then performs the replacement.
> >
> > The .text.alternative_cb section is actually marked as SHF_EXECINSTR | SHF_ALLOC
> > during compilation, so intersections() includes this section and sets it as executable later.
>
> I'm worried there is a chicken-and-egg problem here. What if the
> callback itself requires patching via some other alternative? Is there
> a guarantee that this always performed in the correct order?
Maybe we should just reject loading modules that have alternative
callbacks that don't reside in the kernel text? I _think_ that should
cover all the in-tree users, although I didn't get a reply to my
question asking which module triggered this bug report.
Will
next prev parent reply other threads:[~2025-08-11 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 7:27 [PATCH] arm64/module: Support for patching modules during runtime fanqincui
2025-08-08 11:54 ` Will Deacon
[not found] ` <3d4011c0.6aaa.198981027d7.Coremail.fanqincui@163.com>
2025-08-11 8:01 ` Marc Zyngier
2025-08-11 8:32 ` fanqincui
2025-08-11 8:55 ` Marc Zyngier
2025-08-11 9:57 ` fanqincui
2025-08-11 11:49 ` Marc Zyngier
2025-08-11 12:05 ` Will Deacon [this message]
2025-08-11 12:13 ` Mark Rutland
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=aJnccgC5E-ui2Oqo@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cuifq1@chinatelecom.cn \
--cc=fanqincui@163.com \
--cc=hanht2@chinatelecom.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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