[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yz9m9N9qG2OOdyPy@bombadil.infradead.org>
Date: Thu, 6 Oct 2022 16:38:28 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Song Liu <song@...nel.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, x86@...nel.org, peterz@...radead.org,
hch@....de, kernel-team@...com, rick.p.edgecombe@...el.com,
dave.hansen@...el.com
Subject: Re: [RFC 3/5] modules, x86: use vmalloc_exec for module core
On Thu, Aug 18, 2022 at 03:42:16PM -0700, Song Liu wrote:
> diff --git a/arch/x86/kernel/module.c b/arch/x86/kernel/module.c
> index 100446ffdc1d..570af623e28f 100644
> --- a/arch/x86/kernel/module.c
> +++ b/arch/x86/kernel/module.c
> @@ -229,6 +229,7 @@ int apply_relocate_add(Elf64_Shdr *sechdrs,
> bool early = me->state == MODULE_STATE_UNFORMED;
> void *(*write)(void *, const void *, size_t) = memcpy;
>
> + early = false;
> if (!early) {
> write = text_poke;
> mutex_lock(&text_mutex);
As per 88fc078a7a8f6 ("x86/module: Use text_poke() for late
relocations") I'm curious why we have to take the live patching
path now all the time?
Luis
Powered by blists - more mailing lists