Re: [PATCH bpf-next v2 0/5] execmem_alloc for BPF programs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2022-11-15 at 13:18 -0800, Luis Chamberlain wrote:
> The main hurdles for modules are:
> 
>   * x86 needs support for CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC
>     to use this properly
>   * in light of lack of support for
> CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC
>     we need a fallback
>   * today module_alloc() follows special hanky panky open coded
> semantics for
>     special page permissions, a unified way to handle this would be
>     ideal instead of expecting everyone to get it right.

How were you thinking non-text_poke() architectures load their text
into the text region without the fallback method? Split logic in cross
arch modules.c? Sorry if this is changed, but last time I was in there
I remember there was quite a bit of cross-arch code loading text.




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux