All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: fanqincui  <fanqincui@163.com>
Cc: "Will Deacon" <will@kernel.org>,
	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 12:49:28 +0100	[thread overview]
Message-ID: <86wm7a84dz.wl-maz@kernel.org> (raw)
In-Reply-To: <56b98f57.954f.1989890838d.Coremail.fanqincui@163.com>

On Mon, 11 Aug 2025 10:57:44 +0100,
fanqincui <fanqincui@163.com> wrote:
>
> >Well, you can't know about that. We patch basic primitives such as
> >atomics, system register access, and plenty of other things. These
> >things need to interoperate with the rest of the kernel.
> >
> >It's already difficult to guarantee inside the kernel itself. Having
> >it in random modules will be even harder.
> >
> 
> 
> Okay, so the kernel patches you mentioned, are they already patched
> when the module is installed?

Yes.

> This doesn't conflict with the kernel patching.

In what sense?

> I mean, the specific patching within the module is up to me.

No.

> If the chicken-and-egg problem you mentioned exist, module
> developers should avoid it in their own code. 

We're not in the business of making the kernel more fragile and hard
to maintain than it already is. So either it *always* works, or it is
completely disallowed.

> I think the kernel should provide modules with the ability to patch
> themselves, right?

Only if it is safe to do so. Which is why I asked a question in my
initial reply, which you still haven't answered.

	M.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2025-08-11 11:52 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 [this message]
2025-08-11 12:05       ` Will Deacon
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=86wm7a84dz.wl-maz@kernel.org \
    --to=maz@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=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.