Re: [RFC][PATCH 1/4] module: mm: Make module_alloc() generally available

On Thursday 03/07 at 14:43 +, Christophe Leroy wrote: > Hi Calvin, > > Le 06/03/2024 à 21:05, Calvin Owens a écrit : > > [Vous ne recevez pas souvent de courriers de jcalvinow...@gmail.com. > > Découvrez pourquoi ceci est important à > > https://aka.ms/LearnAboutSenderIdentification ] > >

Re: [RFC][PATCH 1/4] module: mm: Make module_alloc() generally available

On Friday 03/08 at 11:16 +0900, Masami Hiramatsu wrote: > Hi Calvin, > > On Wed, 6 Mar 2024 12:05:08 -0800 > Calvin Owens wrote: > > > Both BPF_JIT and KPROBES depend on CONFIG_MODULES, but only require > > module_alloc() itself, which can be easily separated into a standalone > > allocator

Re: [RFC][PATCH 1/4] module: mm: Make module_alloc() generally available

Hi Calvin, On Wed, 6 Mar 2024 12:05:08 -0800 Calvin Owens wrote: > Both BPF_JIT and KPROBES depend on CONFIG_MODULES, but only require > module_alloc() itself, which can be easily separated into a standalone > allocator for executable kernel memory. Thanks for your work! As Luis pointed, it

Re: [RFC][PATCH 1/4] module: mm: Make module_alloc() generally available

Hi Calvin, Le 06/03/2024 à 21:05, Calvin Owens a écrit : > [Vous ne recevez pas souvent de courriers de jcalvinow...@gmail.com. > Découvrez pourquoi ceci est important à > https://aka.ms/LearnAboutSenderIdentification ] > > Both BPF_JIT and KPROBES depend on CONFIG_MODULES, but only require >

[RFC][PATCH 1/4] module: mm: Make module_alloc() generally available

Both BPF_JIT and KPROBES depend on CONFIG_MODULES, but only require module_alloc() itself, which can be easily separated into a standalone allocator for executable kernel memory. Thomas Gleixner sent a patch to do that for x86 as part of a larger series a couple years ago: