riscv: improve self-protection
Subsystems (8)
cover riscv: improve self-protection
From: Jisheng Zhang <[email protected]>
patch1 is a trivial improvement patch to move some functions to .init section
Then following patches improve self-protection by:
Marking some variables __ro_after_init
Constifing some variables
Enabling ARCH_HAS_STRICT_MODULE_RWX
Jisheng Zhang (9):
riscv: add __init section marker to some functions
riscv: Mark some global variables __ro_after_init
riscv: Constify sys_call_table
riscv: Constify sbi_ipi_ops
riscv: kprobes: Implement alloc_insn_page()
riscv: bpf: Move bpf_jit_alloc_exec() and bpf_jit_free_exec() to core
riscv: bpf: Avoid breaking W^X
riscv: module: Create module allocations without exec permissions
riscv: Set ARCH_HAS_STRICT_MODULE_RWX if MMU
arch/riscv/Kconfig | 1 + arch/riscv/include/asm/smp.h | 4 ++-- arch/riscv/include/asm/syscall.h | 2 +- arch/riscv/kernel/module.c | 2 +- arch/riscv/kernel/probes/kprobes.c | 8 ++++++++ arch/riscv/kernel/sbi.c | 10 +++++----- arch/riscv/kernel/smp.c | 6 +++--- arch/riscv/kernel/syscall_table.c | 2 +- arch/riscv/kernel/time.c | 2 +- arch/riscv/kernel/traps.c | 2 +- arch/riscv/kernel/vdso.c | 4 ++-- arch/riscv/mm/init.c | 12 ++++++------ arch/riscv/mm/kasan_init.c | 6 +++--- arch/riscv/mm/ptdump.c | 2 +- arch/riscv/net/bpf_jit_comp64.c | 13 ------------- arch/riscv/net/bpf_jit_core.c | 14 ++++++++++++++ 16 files changed, 50 insertions(+), 40 deletions(-)
Signature · 1 line
2.31.0
PATCH 1/9 riscv: add __init section marker to some functions
From: Jisheng Zhang <[email protected]>
They are not needed after booting, so mark them as __init to move them to the __init section.
--- arch/riscv/kernel/traps.c | 2 +- arch/riscv/mm/init.c | 6 +++--- arch/riscv/mm/kasan_init.c | 6 +++--- arch/riscv/mm/ptdump.c | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-)
arch/riscv/kernel/traps.c +1 -1
@@ -197,6 +197,6 @@ int is_valid_bugaddr(unsigned long pc)#endif /* CONFIG_GENERIC_BUG */ /* stvec & scratch is already set from head.S */ -void trap_init (void ) +void __init trap_init (void ) { }
arch/riscv/mm/init.c +3 -3
@@ -57,7 +57,7 @@ static void __init zone_sizes_init(void)free_area_init (max_zone_pfns); } -static void setup_zero_page (void ) +static void __init setup_zero_page (void ) {memset ((void *)empty_zero_page,0 ,PAGE_SIZE ); }
@@ -75,7 +75,7 @@ static inline void print_mlm(char *name, unsigned long b, unsigned long t) (((t) - (b)) >> 20)); } -static void print_vm_layout (void ) +static void __init print_vm_layout (void ) {pr_notice ("Virtual kernel memory layout:\n" ); print_mlk("fixmap", (unsigned long)FIXADDR_START,
@@ -557,7 +557,7 @@ static inline void setup_vm_final(void)#endif /* CONFIG_MMU */ #ifdef CONFIG_STRICT_KERNEL_RWX -void protect_kernel_text_data (void ) +void __init protect_kernel_text_data (void ) {unsigned long text_start = (unsigned long )_start;unsigned long init_text_start = (unsigned long )__init_text_begin;
arch/riscv/mm/kasan_init.c +3 -3
@@ -60,7 +60,7 @@ asmlinkage void __init kasan_early_init(void)local_flush_tlb_all (); } -static void kasan_populate_pte (pmd_t *pmd,unsigned long vaddr,unsigned long end) +static void __init kasan_populate_pte (pmd_t *pmd,unsigned long vaddr,unsigned long end) {phys_addr_t phys_addr;pte_t *ptep, *base_pte;
@@ -82,7 +82,7 @@ static void kasan_populate_pte(pmd_t *pmd, unsigned long vaddr, unsigned long enset_pmd (pmd,pfn_pmd (PFN_DOWN (__pa (base_pte)),PAGE_TABLE )); } -static void kasan_populate_pmd (pgd_t *pgd,unsigned long vaddr,unsigned long end) +static void __init kasan_populate_pmd (pgd_t *pgd,unsigned long vaddr,unsigned long end) {phys_addr_t phys_addr;pmd_t *pmdp, *base_pmd;
@@ -117,7 +117,7 @@ static void kasan_populate_pmd(pgd_t *pgd, unsigned long vaddr, unsigned long enset_pgd (pgd,pfn_pgd (PFN_DOWN (__pa (base_pmd)),PAGE_TABLE )); } -static void kasan_populate_pgd (unsigned long vaddr,unsigned long end) +static void __init kasan_populate_pgd (unsigned long vaddr,unsigned long end) {phys_addr_t phys_addr;pgd_t *pgdp =pgd_offset_k (vaddr);
arch/riscv/mm/ptdump.c +1 -1
@@ -331,7 +331,7 @@ static int ptdump_show(struct seq_file *m, void *v)DEFINE_SHOW_ATTRIBUTE (ptdump); -static int ptdump_init (void ) +static int __init ptdump_init (void ) {unsigned int i, j;
Signature · 1 line
2.31.0
PATCH 2/9 riscv: Mark some global variables __ro_after_init
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
All of these are never modified after init, so they can be __ro_after_init.
--- arch/riscv/kernel/sbi.c | 8 ++++---- arch/riscv/kernel/smp.c | 4 ++-- arch/riscv/kernel/time.c | 2 +- arch/riscv/kernel/vdso.c | 4 ++-- arch/riscv/mm/init.c | 6 +++--- 5 files changed, 12 insertions(+), 12 deletions(-)
arch/riscv/kernel/sbi.c +4 -4
@@ -11,14 +11,14 @@#include <asm/smp.h> /* default SBI version is 0.1 */ -unsigned long sbi_spec_version =SBI_SPEC_VERSION_DEFAULT ; +unsigned long sbi_spec_version__ro_after_init =SBI_SPEC_VERSION_DEFAULT ;EXPORT_SYMBOL (sbi_spec_version); -static void (*__sbi_set_timer)(uint64_t stime); -static int (*__sbi_send_ipi)(const unsigned long *hart_mask); +static void (*__sbi_set_timer)(uint64_t stime)__ro_after_init ; +static int (*__sbi_send_ipi)(const unsigned long *hart_mask)__ro_after_init ;static int (*__sbi_rfence)(int fid,const unsigned long *hart_mask,unsigned long start,unsigned long size, -unsigned long arg4,unsigned long arg5); +unsigned long arg4,unsigned long arg5)__ro_after_init ; struct sbiret sbi_ecall(int ext, int fid, unsigned long arg0, unsigned long arg1, unsigned long arg2,
arch/riscv/kernel/smp.c +2 -2
@@ -30,7 +30,7 @@ enum ipi_message_type { IPI_MAX }; -unsigned long __cpuid_to_hartid_map[NR_CPUS ] = { +unsigned long __cpuid_to_hartid_map[NR_CPUS ]__ro_after_init = { [0 ...NR_CPUS -1 ] =INVALID_HARTID };
@@ -85,7 +85,7 @@ static void ipi_stop(void)wait_for_interrupt (); } -static struct riscv_ipi_ops *ipi_ops; +static struct riscv_ipi_ops *ipi_ops__ro_after_init ;void riscv_set_ipi_ops (struct riscv_ipi_ops *ops) {
arch/riscv/kernel/time.c +1 -1
@@ -11,7 +11,7 @@#include <asm/processor.h> #include <asm/timex.h> -unsigned long riscv_timebase; +unsigned long riscv_timebase__ro_after_init ;EXPORT_SYMBOL_GPL (riscv_timebase);void __init time_init (void )
arch/riscv/kernel/vdso.c +2 -2
@@ -20,8 +20,8 @@extern char vdso_start[], vdso_end[]; -static unsigned int vdso_pages; -static struct page **vdso_pagelist; +static unsigned int vdso_pages__ro_after_init ; +static struct page **vdso_pagelist__ro_after_init ;/* * The vDSO data page.
arch/riscv/mm/init.c +3 -3
@@ -149,11 +149,11 @@ void __init setup_bootmem(void) }#ifdef CONFIG_MMU -static struct pt_alloc_ops pt_ops; +static struct pt_alloc_ops pt_ops__ro_after_init ; -unsigned long va_pa_offset; +unsigned long va_pa_offset__ro_after_init ;EXPORT_SYMBOL (va_pa_offset); -unsigned long pfn_base; +unsigned long pfn_base__ro_after_init ;EXPORT_SYMBOL (pfn_base); pgd_t swapper_pg_dir[PTRS_PER_PGD] __page_aligned_bss;
Signature · 1 line
2.31.0
PATCH 3/9 riscv: Constify sys_call_table
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
Constify the sys_call_table so that it will be placed in the .rodata section. This will cause attempts to modify the table to fail when strict page permissions are in place.
--- arch/riscv/include/asm/syscall.h | 2 +- arch/riscv/kernel/syscall_table.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
arch/riscv/include/asm/syscall.h +1 -1
@@ -15,7 +15,7 @@#include <linux/err.h> /* The array of function pointers for syscalls. */ -extern void *sys_call_table[]; +extern void *const sys_call_table[];/* * Only the low 32 bits of orig_r0 are meaningful, so we return int.
arch/riscv/kernel/syscall_table.c +1 -1
@@ -13,7 +13,7 @@#undef __SYSCALL#define __SYSCALL (nr, call) [nr] = (call), -void *sys_call_table[__NR_syscalls] = { +void *const sys_call_table[__NR_syscalls] = { [0 ... __NR_syscalls -1 ] = sys_ni_syscall, #include <asm/unistd.h> };
Signature · 1 line
2.31.0
PATCH 4/9 riscv: Constify sbi_ipi_ops
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
Constify the sbi_ipi_ops so that it will be placed in the .rodata section. This will cause attempts to modify it to fail when strict page permissions are in place.
--- arch/riscv/include/asm/smp.h | 4 ++-- arch/riscv/kernel/sbi.c | 2 +- arch/riscv/kernel/smp.c | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-)
arch/riscv/include/asm/smp.h +2 -2
@@ -46,7 +46,7 @@ int riscv_hartid_to_cpuid(int hartid);void riscv_cpuid_to_hartid_mask (const struct cpumask *in,struct cpumask *out);/* Set custom IPI operations */ -void riscv_set_ipi_ops (struct riscv_ipi_ops *ops); +void riscv_set_ipi_ops (const struct riscv_ipi_ops *ops);/* Clear IPI for current CPU */ void riscv_clear_ipi (void );
@@ -92,7 +92,7 @@ static inline void riscv_cpuid_to_hartid_mask(const struct cpumask *in,cpumask_set_cpu (boot_cpu_hartid, out); } -static inline void riscv_set_ipi_ops (struct riscv_ipi_ops *ops) +static inline void riscv_set_ipi_ops (const struct riscv_ipi_ops *ops) { }
arch/riscv/kernel/sbi.c +1 -1
@@ -556,7 +556,7 @@ static void sbi_send_cpumask_ipi(const struct cpumask *target)sbi_send_ipi (cpumask_bits (&hartid_mask)); } -static struct riscv_ipi_ops sbi_ipi_ops = { +static const struct riscv_ipi_ops sbi_ipi_ops = { .ipi_inject = sbi_send_cpumask_ipi };
arch/riscv/kernel/smp.c +2 -2
@@ -85,9 +85,9 @@ static void ipi_stop(void)wait_for_interrupt (); } -static struct riscv_ipi_ops *ipi_ops__ro_after_init ; +static const struct riscv_ipi_ops *ipi_ops__ro_after_init ; -void riscv_set_ipi_ops (struct riscv_ipi_ops *ops) +void riscv_set_ipi_ops (const struct riscv_ipi_ops *ops) { ipi_ops = ops; }
Signature · 1 line
2.31.0
PATCH 5/9 riscv: kprobes: Implement alloc_insn_page()
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
Allocate PAGE_KERNEL_READ_EXEC(read only, executable) page for kprobes insn page. This is to prepare for STRICT_MODULE_RWX.
--- arch/riscv/kernel/probes/kprobes.c | 8 ++++++++ 1 file changed, 8 insertions(+)
arch/riscv/kernel/probes/kprobes.c +8 -0
@@ -84,6 +84,14 @@ int __kprobes arch_prepare_kprobe(struct kprobe *p)return 0 ; } +void *alloc_insn_page (void ) +{ +return __vmalloc_node_range (PAGE_SIZE ,1 ,VMALLOC_START ,VMALLOC_END , +GFP_KERNEL ,PAGE_KERNEL_READ_EXEC , +VM_FLUSH_RESET_PERMS ,NUMA_NO_NODE , +__builtin_return_address (0 )); +} +/* install breakpoint in text */ void __kprobes arch_arm_kprobe (struct kprobe *p) {
Signature · 1 line
2.31.0
PATCH 6/9 riscv: bpf: Move bpf_jit_alloc_exec() and bpf_jit_free_exec() to core
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
We will drop the executable permissions of the code pages from the mapping at allocation time soon. Move bpf_jit_alloc_exec() and bpf_jit_free_exec() to bpf_jit_core.c so that they can be shared by both RV64I and RV32I.
--- arch/riscv/net/bpf_jit_comp64.c | 13 ------------- arch/riscv/net/bpf_jit_core.c | 13 +++++++++++++ 2 files changed, 13 insertions(+), 13 deletions(-)
arch/riscv/net/bpf_jit_comp64.c +0 -13
@@ -1148,16 +1148,3 @@ void bpf_jit_build_epilogue(struct rv_jit_context *ctx) {__build_epilogue (false, ctx); } - -void *bpf_jit_alloc_exec (unsigned long size) -{ -return __vmalloc_node_range (size,PAGE_SIZE ,BPF_JIT_REGION_START , -BPF_JIT_REGION_END ,GFP_KERNEL , -PAGE_KERNEL_EXEC ,0 ,NUMA_NO_NODE , -__builtin_return_address (0 )); -} - -void bpf_jit_free_exec (void *addr) -{ -return vfree (addr); -}
arch/riscv/net/bpf_jit_core.c +13 -0
@@ -164,3 +164,16 @@ struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *prog) tmp : orig_prog);return prog; } + +void *bpf_jit_alloc_exec (unsigned long size) +{ +return __vmalloc_node_range (size,PAGE_SIZE ,BPF_JIT_REGION_START , +BPF_JIT_REGION_END ,GFP_KERNEL , +PAGE_KERNEL_EXEC ,0 ,NUMA_NO_NODE , +__builtin_return_address (0 )); +} + +void bpf_jit_free_exec (void *addr) +{ +return vfree (addr); +}
Signature · 1 line
2.31.0
Re: [PATCH 6/9] riscv: bpf: Move bpf_jit_alloc_exec() and bpf_jit_free_exec() to core
Quoted 4 lines
We will drop the executable permissions of the code pages from the mapping at allocation time soon. Move
bpf_jit_alloc_exec()andbpf_jit_free_exec()tobpf_jit_core.cso that they can be shared by both RV64I and RV32I.
Looks good to me.
PATCH 7/9 riscv: bpf: Avoid breaking W^X
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
We allocate Non-executable pages, then call bpf_jit_binary_lock_ro() to enable executable permission after mapping them read-only. This is to prepare for STRICT_MODULE_RWX in following patch.
--- arch/riscv/net/bpf_jit_core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/riscv/net/bpf_jit_core.c +2 -1
@@ -152,6 +152,7 @@ struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *prog)bpf_flush_icache (jit_data->header, ctx->insns + ctx->ninsns);if (!prog->is_func || extra_pass) { +bpf_jit_binary_lock_ro (header); out_offset:kfree (ctx->offset);kfree (jit_data);
@@ -169,7 +170,7 @@ void *bpf_jit_alloc_exec(unsigned long size) {return __vmalloc_node_range (size,PAGE_SIZE ,BPF_JIT_REGION_START ,BPF_JIT_REGION_END ,GFP_KERNEL , -PAGE_KERNEL_EXEC ,0 ,NUMA_NO_NODE , +PAGE_KERNEL ,0 ,NUMA_NO_NODE ,__builtin_return_address (0 )); }
Signature · 1 line
2.31.0
kernel test robot
build botRe: [PATCH 7/9] riscv: bpf: Avoid breaking W^X
I love your patch! Yet something to improve:
Hi Jisheng,
I love your patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
[also build test ERROR on bpf/master linus/master v5.12-rc5] [cannot apply to next-20210330]
[If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Jisheng-Zhang/riscv-improve-self-protection/20210330-023324 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master config: riscv-randconfig-r026-20210330 (attached as .config) compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 482283042f795ecc27838a3b2f76b5494991401c)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/0day-ci/linux/commit/8291e9d78fc2eb2438c93001ab65dfe1743a97f2
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jisheng-Zhang/riscv-improve-self-protection/20210330-023324 git checkout 8291e9d78fc2eb2438c93001ab65dfe1743a97f2
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
All errors (new ones prefixed by >>):
>> arch/riscv/net/bpf_jit_core.c:155:26: error: use of undeclared identifier 'header'
bpf_jit_binary_lock_ro(header);
^1 error generated.
vim +/header +155 arch/riscv/net/bpf_jit_core.c
41
42 struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *prog)
43 {
44 bool tmp_blinded = false, extra_pass = false;
45 struct bpf_prog *tmp, *orig_prog = prog;
46 int pass = 0, prev_ninsns = 0, i;
47 struct rv_jit_data *jit_data;
48 struct rv_jit_context *ctx;
49 unsigned int image_size = 0;
50
51 if (!prog->jit_requested)
52 return orig_prog;
53
54 tmp = bpf_jit_blind_constants(prog);
55 if (IS_ERR(tmp))
56 return orig_prog;
57 if (tmp != prog) {
58 tmp_blinded = true;
59 prog = tmp;
60 }
61
62 jit_data = prog->aux->jit_data;
63 if (!jit_data) {
64 jit_data = kzalloc(sizeof(*jit_data), GFP_KERNEL);
65 if (!jit_data) {
66 prog = orig_prog;
67 goto out;
68 }
69 prog->aux->jit_data = jit_data;
70 }
71
72 ctx = &jit_data->ctx;
73
74 if (ctx->offset) {
75 extra_pass = true;
76 image_size = sizeof(*ctx->insns) * ctx->ninsns;
77 goto skip_init_ctx;
78 }
79
80 ctx->prog = prog;
81 ctx->offset = kcalloc(prog->len, sizeof(int), GFP_KERNEL);
82 if (!ctx->offset) {
83 prog = orig_prog;
84 goto out_offset;
85 }
86 for (i = 0; i < prog->len; i++) {
87 prev_ninsns += 32;
88 ctx->offset[i] = prev_ninsns;
89 }
90
91 for (i = 0; i < NR_JIT_ITERATIONS; i++) {
92 pass++;
93 ctx->ninsns = 0;
94 if (build_body(ctx, extra_pass, ctx->offset)) {
95 prog = orig_prog;
96 goto out_offset;
97 }
98 bpf_jit_build_prologue(ctx);
99 ctx->epilogue_offset = ctx->ninsns;
100 bpf_jit_build_epilogue(ctx);
101
102 if (ctx->ninsns == prev_ninsns) {
103 if (jit_data->header)
104 break;
105
106 image_size = sizeof(*ctx->insns) * ctx->ninsns;
107 jit_data->header =
108 bpf_jit_binary_alloc(image_size,
109 &jit_data->image,
110 sizeof(u32),
111 bpf_fill_ill_insns);
112 if (!jit_data->header) {
113 prog = orig_prog;
114 goto out_offset;
115 }
116
117 ctx->insns = (u16 *)jit_data->image;
118 /*
119 * Now, when the image is allocated, the image can
120 * potentially shrink more (auipc/jalr -> jal).
121 */
122 }
123 prev_ninsns = ctx->ninsns;
124 }
125
126 if (i == NR_JIT_ITERATIONS) {
127 pr_err("bpf-jit: image did not converge in <%d passes!\n", i);
128 bpf_jit_binary_free(jit_data->header);
129 prog = orig_prog;
130 goto out_offset;
131 }
132
133 skip_init_ctx:
134 pass++;
135 ctx->ninsns = 0;
136
137 bpf_jit_build_prologue(ctx);
138 if (build_body(ctx, extra_pass, NULL)) {
139 bpf_jit_binary_free(jit_data->header);
140 prog = orig_prog;
141 goto out_offset;
142 }
143 bpf_jit_build_epilogue(ctx);
144
145 if (bpf_jit_enable > 1)
146 bpf_jit_dump(prog->len, image_size, pass, ctx->insns);
147
148 prog->bpf_func = (void *)ctx->insns;
149 prog->jited = 1;
150 prog->jited_len = image_size;
151
152 bpf_flush_icache(jit_data->header, ctx->insns + ctx->ninsns);
153
154 if (!prog->is_func || extra_pass) {
> 155 bpf_jit_binary_lock_ro(header); 156 out_offset:
157 kfree(ctx->offset);
158 kfree(jit_data);
159 prog->aux->jit_data = NULL;
160 }
161 out:
162
163 if (tmp_blinded)
164 bpf_jit_prog_release_other(prog, prog == orig_prog ?
165 tmp : orig_prog);
166 return prog;
167 }
168
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Re: [PATCH 7/9] riscv: bpf: Avoid breaking W^X
In reply to Jisheng ZhangQuoted 5 lines · Jisheng Zhang
From: Jisheng Zhang <[email protected]>
We allocate Non-executable pages, then call
bpf_jit_binary_lock_ro()to enable executable permission after mapping them read-only. This is to prepare forSTRICT_MODULE_RWXin following patch.
That breaks booting with
<https://github.com/openSUSE/kernel-source/blob/master/config/riscv64/default>.
Andreas.
Signature · 3 lines
Andreas Schwab, [email protected] GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: [PATCH 7/9] riscv: bpf: Avoid breaking W^X
Hi Andreas,
Quoted 11 lines · On Fri, 11 Jun 2021 16:10:03 +0200 Andreas Schwab <[email protected]> wrote:
Quoted 5 lines · Jisheng Zhang
From: Jisheng Zhang <[email protected]>
We allocate Non-executable pages, then call
bpf_jit_binary_lock_ro()to enable executable permission after mapping them read-only. This is to prepare forSTRICT_MODULE_RWXin following patch.That breaks booting with
<https://github.com/openSUSE/kernel-source/blob/master/config/riscv64/default>.
Thanks for the bug report.
I reproduced an kernel panic with the defconfig on qemu, but I'm not sure whether this is the issue you saw, I will check.
0.161959] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.167028] pinctrl core: initialized pinctrl subsystem [ 0.190727] Unable to handle kernel paging request at virtual address ffffffff81651bd8 [ 0.191361] Oops [#1] [ 0.191509] Modules linked in: [ 0.191814] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #3 [ 0.192179] Hardware name: riscv-virtio,qemu (DT) [ 0.192492] epc : __memset+0xc4/0xfc [ 0.192712] ra : skb_flow_dissector_init+0x22/0x86 [ 0.192915] epc : ffffffff803e2700 ra : ffffffff8058f90c sp : ffffffe001a4fda0 [ 0.193221] gp : ffffffff8156d120 tp : ffffffe001a5b700 t0 : ffffffff81651b10 [ 0.193631] t1 : 0000000000000100 t2 : 00000000000003a8 s0 : ffffffe001a4fdd0 [ 0.194034] s1 : ffffffff80c9e250 a0 : ffffffff81651bd8 a1 : 0000000000000000 [ 0.194502] a2 : 000000000000003c a3 : ffffffff81651c10 a4 : 0000000000000064 [ 0.195053] a5 : ffffffff803e2700 a6 : 0000000000000040 a7 : 0000000000000002 [ 0.195436] s2 : ffffffff81651bd8 s3 : 0000000000000009 s4 : ffffffff8156e0c8 [ 0.195723] s5 : ffffffff8156e050 s6 : ffffffff80a105e0 s7 : ffffffff80a00738 [ 0.195992] s8 : ffffffff80f07be0 s9 : 0000000000000008 s10: ffffffff808000ac [ 0.196257] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.196511] t5 : 00000000000003a9 t6 : 00000000000003ff [ 0.196714] status: 0000000000000120 badaddr: ffffffff81651bd8 cause: 000000000000000f [ 0.197103] [<ffffffff803e2700>] __memset+0xc4/0xfc [ 0.197408] [<ffffffff80831f58>] init_default_flow_dissectors+0x22/0x60 [ 0.197693] [<ffffffff800020fc>] do_one_initcall+0x3e/0x168 [ 0.197907] [<ffffffff80801438>] kernel_init_freeable+0x25a/0x2c6 [ 0.198157] [<ffffffff8070a8a8>] kernel_init+0x12/0x110 [ 0.198351] [<ffffffff8000333a>] ret_from_exception+0x0/0xc [ 0.198973] Unable to handle kernel paging request at virtual address ffffffff8164d860 [ 0.199242] Oops [#2] [ 0.199336] Modules linked in: [ 0.199514] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G D 5.13.0-rc5-default+ #3 [ 0.199785] Hardware name: riscv-virtio,qemu (DT) [ 0.199940] epc : _raw_spin_lock_irqsave+0x14/0x4e [ 0.200113] ra : _extract_crng+0x58/0xac [ 0.200264] epc : ffffffff807117ae ra : ffffffff80490774 sp : ffffffe001a4fa70 [ 0.200489] gp : ffffffff8156d120 tp : ffffffe001a5b700 t0 : ffffffff8157c0d7 [ 0.200715] t1 : ffffffff8157c0c8 t2 : 0000000000000000 s0 : ffffffe001a4fa80 [ 0.200938] s1 : ffffffff8164d818 a0 : 0000000000000022 a1 : ffffffe001a4fac8 [ 0.201166] a2 : 0000000000000010 a3 : 0000000000000001 a4 : ffffffff8164d860 [ 0.201389] a5 : 0000000000000000 a6 : c0000000ffffdfff a7 : ffffffffffffffff [ 0.201612] s2 : ffffffff8156e1c0 s3 : ffffffe001a4fac8 s4 : ffffffff8164d860 [ 0.201836] s5 : ffffffff8156e0c8 s6 : ffffffff80a105e0 s7 : ffffffff80a00738 [ 0.202060] s8 : ffffffff80f07be0 s9 : 0000000000000008 s10: ffffffff808000ac [ 0.202295] s11: 0000000000000000 t3 : 000000000000005b t4 : ffffffffffffffff [ 0.202519] t5 : 00000000000003a9 t6 : ffffffe001a4f9b8 [ 0.202691] status: 0000000000000100 badaddr: ffffffff8164d860 cause: 000000000000000f [ 0.202940] [<ffffffff807117ae>] _raw_spin_lock_irqsave+0x14/0x4e [ 0.203326] Unable to handle kernel paging request at virtual address ffffffff8164d860 [ 0.203574] Oops [#3] [ 0.203664] Modules linked in: [ 0.203784] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G D 5.13.0-rc5-default+ #3 [ 0.204046] Hardware name: riscv-virtio,qemu (DT) [ 0.204201] epc : _raw_spin_lock_irqsave+0x14/0x4e [ 0.204371] ra : _extract_crng+0x58/0xac [ 0.204519] epc : ffffffff807117ae ra : ffffffff80490774 sp : ffffffe001a4f740 [ 0.204819] gp : ffffffff8156d120 tp : ffffffe001a5b700 t0 : ffffffff8157c0d7 [ 0.205089] t1 : ffffffff8157c0c8 t2 : 0000000000000000 s0 : ffffffe001a4f750 [ 0.205330] s1 : ffffffff8164d818 a0 : 0000000000000102 a1 : ffffffe001a4f798 [ 0.205553] a2 : 0000000000000010 a3 : 0000000000000001 a4 : ffffffff8164d860 [ 0.205768] a5 : 0000000000000000 a6 : c0000000ffffdfff a7 : ffffffff81408a40 [ 0.205981] s2 : ffffffff8156e1c0 s3 : ffffffe001a4f798 s4 : ffffffff8164d860 [ 0.206197] s5 : ffffffff8156e0c8 s6 : ffffffff80a105e0 s7 : ffffffff80a00738 [ 0.206411] s8 : ffffffff80f07be0 s9 : 0000000000000008 s10: ffffffff808000ac [ 0.206633] s11: 0000000000000000 t3 : 000000000000005b t4 : ffffffffffffffff [ 0.206849] t5 : 00000000000003a9 t6 : ffffffe001a4f688
Re: [PATCH 7/9] riscv: bpf: Avoid breaking W^X
Quoted 12 lines · Jisheng Zhang
I reproduced an kernel panic with the defconfig on qemu, but I'm not sure whether this is the issue you saw, I will check.
0.161959] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.167028] pinctrl core: initialized pinctrl subsystem [ 0.190727] Unable to handle kernel paging request at virtual address ffffffff81651bd8 [ 0.191361] Oops [#1] [ 0.191509] Modules linked in: [ 0.191814] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #3 [ 0.192179] Hardware name: riscv-virtio,qemu (DT) [ 0.192492] epc : __memset+0xc4/0xfc [ 0.192712] ra : skb_flow_dissector_init+0x22/0x86
Yes, that's the same.
Andreas.
Signature · 3 lines
Andreas Schwab, [email protected] GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: [PATCH 7/9] riscv: bpf: Avoid breaking W^X
Hi,
Quoted 15 lines · On Fri, 11 Jun 2021 18:41:16 +0200 Andreas Schwab <[email protected]> wrote:
Quoted 12 lines · Jisheng Zhang
I reproduced an kernel panic with the defconfig on qemu, but I'm not sure whether this is the issue you saw, I will check.
0.161959] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.167028] pinctrl core: initialized pinctrl subsystem [ 0.190727] Unable to handle kernel paging request at virtual address ffffffff81651bd8 [ 0.191361] Oops [#1] [ 0.191509] Modules linked in: [ 0.191814] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #3 [ 0.192179] Hardware name: riscv-virtio,qemu (DT) [ 0.192492] epc : __memset+0xc4/0xfc [ 0.192712] ra : skb_flow_dissector_init+0x22/0x86
Quoted 4 lines
Yes, that's the same.
Andreas.
I think I found the root cause: commit 2bfc6cd81bd ("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:
#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end)
The &_end is unlikely aligned with PMD SIZE, so the front bpf jit region sits with kernel .data section in one PMD. But kenrel is mapped in PMD SIZE, so when bpf_jit_binary_lock_ro() is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write, for example memset the .data section, MMU will trigger store page fault.
To fix the issue, we need to make the bpf jit region PMD size aligned by either patch BPF_JIT_REGION_START to align on PMD size rather than PAGE SIZE, or something as below patch to move the BPF region before modules region:
arch/riscv/include/asm/pgtable.h +3 -3
@@ -31,8 +31,8 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT /* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_VADDR)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
@@ -40,8 +40,8 @@/* Modules always live before the kernel */ #ifdef CONFIG_64BIT -#define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G)#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_VADDR (MODULES_END - SZ_128M)#endif
can you please try it? Per my test, the issue is fixed.
Thanks
Re: [PATCH 7/9] riscv: bpf: Avoid breaking W^X
Quoted 40 lines · Jisheng Zhang
I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:#define
BPF_JIT_REGION_STARTPFN_ALIGN((unsigned long)&_end)The
&_endis unlikely aligned with PMD SIZE, so the front bpf jit region sits with kernel .data section in one PMD. But kenrel is mapped in PMD SIZE, so whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write, for example memset the .data section, MMU will trigger store page fault.To fix the issue, we need to make the bpf jit region PMD size aligned by either patch
BPF_JIT_REGION_STARTto align on PMD size rather than PAGE SIZE, or something as below patch to move the BPF region before modules region:arch/riscv/include/asm/pgtable.h +3
-3@@ -31,8 +31,8 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT /* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_VADDR)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)@@ -40,8 +40,8 @@/* Modules always live before the kernel */ #ifdef CONFIG_64BIT -#define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G)#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_VADDR (MODULES_END - SZ_128M)#endif
Quoted 1 line
can you please try it? Per my test, the issue is fixed.
I can confirm that this fixes the issue.
Andreas.
Signature · 3 lines
Andreas Schwab, [email protected] GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
PATCH 1/1 riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
From: Jisheng Zhang <[email protected]>
Andreas reported commit fc8504765ec5 ("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of config file, I reproduced a kernel panic with the config:
[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---
After some investigation, I think I found the root cause: commit 2bfc6cd81bd ("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:
The &_end is unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, when bpf_jit_binary_lock_ro() is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.
To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
--- arch/riscv/include/asm/pgtable.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
arch/riscv/include/asm/pgtable.h +2 -3
@@ -30,9 +30,8 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
Signature · 1 line
2.32.0
Daniel Borkmann
maintainerRe: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Quoted 60 lines · Jisheng Zhang
From: Jisheng Zhang <[email protected]>
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of config file, I reproduced a kernel panic with the config:[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:The
&_endis unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/include/asm/pgtable.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)arch/riscv/include/asm/pgtable.h +0
-0@@ -30,9 +30,8 @@
arch/riscv/include/asm/pgtable.h line 37
Quoted 10 lines
arch/riscv/include/asm/pgtable.h +2
-3#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
I presume this fix will be routed via riscv tree?
Thanks,
Daniel
Alex Ghiti
reviewerRe: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
In reply to Jisheng ZhangHi Jisheng,
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 37 lines
From: Jisheng Zhang <[email protected]>
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of config file, I reproduced a kernel panic with the config:[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:
Quoted 6 lines
The
&_endis unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.
Good catch, we make sure no physical allocation happens between _end and the next PMD aligned address, but I missed this one.
Quoted 4 lines
To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align BPF_JIT_REGION_START to the next PMD aligned address?
Again, good catch, thanks,
Alex
Quoted 24 lines
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/include/asm/pgtable.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)arch/riscv/include/asm/pgtable.h +2
-3@@ -30,9 +30,8 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
Re: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 54 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 37 lines
From: Jisheng Zhang <[email protected]>
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of config file, I reproduced a kernel panic with the config:[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 6 lines
The
&_endis unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 4 lines
To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
Quoted 5 lines
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?
Originally, I planed to fix the issue by aligning BPF_JIT_REGION_START, but IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF" feature, there's a risk that BPF JIT region is beyond the 2GB of module region:
------
module
------
kernel
------BPF_JIT
So I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
To address "make sure modules and BPF programs get their own virtual regions", what about something as below (applied against this patch)?
arch/riscv/include/asm/pgtable.h +2 -2
@@ -31,7 +31,7 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start))#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
@@ -40,7 +40,7 @@/* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END)#endif
Quoted 29 lines
Again, good catch, thanks,
Alex
Quoted 24 lines
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/include/asm/pgtable.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)arch/riscv/include/asm/pgtable.h +2
-3@@ -30,9 +30,8 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
Alex Ghiti
reviewerRe: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Le 16/06/2021 à 02:03, Jisheng Zhang a écrit :
Quoted 78 lines
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 54 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 37 lines
From: Jisheng Zhang <[email protected]>
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of config file, I reproduced a kernel panic with the config:[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 6 lines
The
&_endis unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 4 lines
To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
Quoted 5 lines
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF" feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JIT
Quoted 3 lines
So I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
From what I read in the lwn article, I'm not sure BPF programs can call module functions, can someone tell us if it is possible? Or planned?
Quoted 17 lines
To address "make sure modules and BPF programs get their own virtual regions", what about something as below (applied against this patch)?
arch/riscv/include/asm/pgtable.h +1
-1@@ -31,7 +31,7 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start))#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
arch/riscv/include/asm/pgtable.h line 46
Quoted 8 lines
arch/riscv/include/asm/pgtable.h +1
-1@@ -40,7 +40,7 @@/* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END)#endif
In case it is possible, I would let the vmalloc allocator handle the case where modules steal room from BPF: I would then not implement the above but rather your first patch.
And do not forget to modify Documentation/riscv/vm-layout.rst accordingly and remove the comment "/* KASLR should leave at least 128MB for BPF after the kernel */"
Thanks,
Alex
Quoted 38 lines
Quoted 19 lines
Again, good catch, thanks,
Alex
Quoted 13 lines
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/include/asm/pgtable.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)arch/riscv/include/asm/pgtable.h +0
-0@@ -30,9 +30,8 @@Quoted 11 lines
arch/riscv/include/asm/pgtable.h line 37
Quoted 11 lines
arch/riscv/include/asm/pgtable.h +2
-3#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Re: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Quoted 79 lines · On Thu, 17 Jun 2021 09:23:04 +0200 Alex Ghiti <[email protected]> wrote:
Le 16/06/2021 à 02:03, Jisheng Zhang a écrit :
Quoted 78 lines
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 54 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 37 lines
From: Jisheng Zhang <[email protected]>
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of config file, I reproduced a kernel panic with the config:[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 6 lines
The
&_endis unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 4 lines
To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
Quoted 5 lines
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF" feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JIT
Quoted 6 lines
Quoted 3 lines
So I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
From what I read in the lwn article, I'm not sure BPF programs can call
module functions, can someone tell us if it is possible? Or planned?
What about module call BPF program? this case also wants the 2GB address limit.
Quoted 31 lines
Quoted 18 lines
To address "make sure modules and BPF programs get their own virtual regions", what about something as below (applied against this patch)?
arch/riscv/include/asm/pgtable.h +1
-1@@ -31,7 +31,7 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start))#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)arch/riscv/include/asm/pgtable.h line 46
Quoted 8 lines
arch/riscv/include/asm/pgtable.h +1
-1@@ -40,7 +40,7 @@/* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END)#endif In case it is possible, I would let the vmalloc allocator handle the case where modules steal room from BPF: I would then not implement the above but rather your first patch.
Quoted 3 lines
And do not forget to modify
Documentation/riscv/vm-layout.rstaccordingly and remove the comment "/* KASLR should leave at least 128MB for BPF after the kernel */"
Thanks for the comments
Palmer Dabbelt
maintainerRe: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
In reply to Jisheng ZhangQuoted 120 lines · On Tue, 15 Jun 2021 17:03:28 PDT (-0700), [email protected] wrote:
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 46 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 37 lines
From: Jisheng Zhang <[email protected]>
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of config file, I reproduced a kernel panic with the config:[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 6 lines
The
&_endis unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.Quoted 8 lines
Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 4 lines
To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF" feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JITSo I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
To address "make sure modules and BPF programs get their own virtual regions", what about something as below (applied against this patch)?
arch/riscv/include/asm/pgtable.h +2
-2@@ -31,7 +31,7 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start))#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)@@ -40,7 +40,7 @@/* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END)#endif Quoted 19 lines
Again, good catch, thanks,
Alex
Quoted 13 lines
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/include/asm/pgtable.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)arch/riscv/include/asm/pgtable.h +0
-0@@ -30,9 +30,8 @@
Quoted 11 lines
Quoted 11 lines
arch/riscv/include/asm/pgtable.h line 37
Quoted 11 lines
arch/riscv/include/asm/pgtable.h +2
-3#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
This, when applied onto fixes, is breaking early boot on KASAN configurations for me.
Alex Ghiti
reviewerRe: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Le 17/06/2021 à 09:30, Palmer Dabbelt a écrit :
Quoted 135 lines · On Tue, 15 Jun 2021 17:03:28 PDT (-0700), [email protected] wrote:
Quoted 134 lines
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 57 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 2 lines
From: Jisheng Zhang <[email protected]>
Quoted 1 line
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breakingW^X")
Quoted 1 line
breaks booting with one kind of config file, I reproduced a kernel
panic
Quoted 2 lines
with the config:
Quoted 1 line
[ 0.138553] Unable to handle kernel paging request at virtual
address
ffffffff81201220Quoted 3 lines
[ 0.139159] Oops [#1]
[ 0.139303] Modules linked in:
[ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted5.13.0-rc5-default+ #1
Quoted 4 lines
[ 0.139934] Hardware name: riscv-virtio,qemu (DT)
[ 0.140193] epc :__memset+0xc4/0xfc
[ 0.140416] ra :skb_flow_dissector_init+0x1e/0x82[ 0.140609] epc :ffffffff8029806cra :ffffffff8033be78sp :
ffffffe001647da0Quoted 1 line
[ 0.140878] gp :
ffffffff81134b08tp :ffffffe001654380t0 :
ffffffff81201158Quoted 1 line
[ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 :
ffffffe001647dd0Quoted 1 line
[ 0.141424] s1 :
ffffffff80a43250a0 :ffffffff81201220a1 :0000000000000000
Quoted 1 line
[ 0.141654] a2 :
000000000000003ca3 :ffffffff81201258a4 :0000000000000064
Quoted 1 line
[ 0.141893] a5 :
ffffffff8029806ca6 : 0000000000000040 a7 :ffffffffffffffff
Quoted 1 line
[ 0.142126] s2 :
ffffffff81201220s3 : 0000000000000009 s4 :
ffffffff81135088Quoted 1 line
[ 0.142353] s5 :
ffffffff81135038s6 :ffffffff8080ce80s7 :
ffffffff80800438Quoted 1 line
[ 0.142584] s8 :
ffffffff80bc6578s9 : 0000000000000008 s10:
ffffffff806000acQuoted 1 line
[ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 :
0000000000000000
Quoted 2 lines
[ 0.143042] t5 : 0000000000000155 t6 :
00000000000003ff[ 0.143220] status: 0000000000000120 badaddr:ffffffff81201220cause:
000000000000000fQuoted 2 lines
[ 0.143560] [<
ffffffff8029806c>]__memset+0xc4/0xfc[ 0.143859] [<ffffffff8061e984>]init_default_flow_dissectors+0x22/0x60 > [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 > [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 > [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 > [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xcQuoted 10 lines
[ 0.145124] ---[ end trace
f1e9643daa46d591]---Quoted 1 line
After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 1 line
The
&_endis unlikely aligned with PMD size, so the front bpf jitregion sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, when
bpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.Quoted 6 lines
Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 3 lines
Quoted 1 line
To fix the issue, we need to ensure the BPF JIT region is PMD size
aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section.
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF" feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JITSo I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
To address "make sure modules and BPF programs get their own virtual regions", what about something as below (applied against this patch)?
arch/riscv/include/asm/pgtable.h +2
-2@@ -31,7 +31,7 @@ #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start)) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) #define BPF_JIT_REGION_END (VMALLOC_END)@@ -40,7 +40,7 @@ /* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END) #endifQuoted 24 lines
Again, good catch, thanks,
Alex
Quoted 6 lines
Quoted 1 line
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>---
arch/riscv/include/asm/pgtable.h| 5 ++---1 file changed, 2 insertions(+), 3 deletions(-)Review
Quoted 1 line
(quoted diff) +0
-0
b/arch/riscv/include/asm/pgtable.harch/riscv/include/asm/pgtable.h line 34
Quoted 9 lines
index
9469f464e71a..380cd3a7e548100644arch/riscv/include/asm/pgtable.h +0
-3@@ -30,9 +30,8 @@ > #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START +
BPF_JIT_REGION_SIZE)Quoted 1 line
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_START (BPF_JIT_REGION_END -
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
BPF_JIT_REGION_SIZE)Quoted 5 lines
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_END (MODULES_END) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) #define BPF_JIT_REGION_END (VMALLOC_END)This, when applied onto fixes, is breaking early boot on KASAN configurations for me.
Not surprising, I took a shortcut when initializing KASAN for modules, kernel and BPF:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));
The kernel is then not covered, I'm taking a look at how to fix that properly.
Quoted 5 lines
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Alex Ghiti
reviewerRe: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Le 17/06/2021 à 10:09, Alex Ghiti a écrit :
Quoted 148 lines
Le 17/06/2021 à 09:30, Palmer Dabbelt a écrit :
Quoted 138 lines · On Tue, 15 Jun 2021 17:03:28 PDT (-0700), [email protected] wrote:
Quoted 137 lines
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 59 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 2 lines
From: Jisheng Zhang <[email protected]>
Quoted 1 line
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoidbreaking W^X")
Quoted 1 line
breaks booting with one kind of config file, I reproduced a kernel
panic
Quoted 2 lines
with the config:
Quoted 1 line
[ 0.138553] Unable to handle kernel paging request at virtual
address
ffffffff81201220Quoted 3 lines
[ 0.139159] Oops [#1]
[ 0.139303] Modules linked in:
[ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted5.13.0-rc5-default+ #1
Quoted 4 lines
[ 0.139934] Hardware name: riscv-virtio,qemu (DT)
[ 0.140193] epc :__memset+0xc4/0xfc
[ 0.140416] ra :skb_flow_dissector_init+0x1e/0x82[ 0.140609] epc :ffffffff8029806cra :ffffffff8033be78sp :
ffffffe001647da0Quoted 1 line
[ 0.140878] gp :
ffffffff81134b08tp :ffffffe001654380t0 :
ffffffff81201158Quoted 1 line
[ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 :
ffffffe001647dd0Quoted 1 line
[ 0.141424] s1 :
ffffffff80a43250a0 :ffffffff81201220a1 :0000000000000000
Quoted 1 line
[ 0.141654] a2 :
000000000000003ca3 :ffffffff81201258a4 :0000000000000064
Quoted 1 line
[ 0.141893] a5 :
ffffffff8029806ca6 : 0000000000000040 a7 :ffffffffffffffff
Quoted 1 line
[ 0.142126] s2 :
ffffffff81201220s3 : 0000000000000009 s4 :
ffffffff81135088Quoted 1 line
[ 0.142353] s5 :
ffffffff81135038s6 :ffffffff8080ce80s7 :
ffffffff80800438Quoted 1 line
[ 0.142584] s8 :
ffffffff80bc6578s9 : 0000000000000008 s10:
ffffffff806000acQuoted 1 line
[ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 :
0000000000000000
Quoted 2 lines
[ 0.143042] t5 : 0000000000000155 t6 :
00000000000003ff[ 0.143220] status: 0000000000000120 badaddr:ffffffff81201220cause:
000000000000000fQuoted 2 lines
[ 0.143560] [<
ffffffff8029806c>]__memset+0xc4/0xfc[ 0.143859] [<ffffffff8061e984>]init_default_flow_dissectors+0x22/0x60 > [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 > [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 > [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 > [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xcQuoted 6 lines
[ 0.145124] ---[ end trace
f1e9643daa46d591]---Quoted 1 line
After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 1 line
The
&_endis unlikely aligned with PMD size, so the front bpf jitregion sits with part of kernel .data section in one PMD size
mapping.
Quoted 2 lines
But kernel is mapped in PMD SIZE, when
bpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part ofkernel
Quoted 2 lines
.data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.
Quoted 7 lines
Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 2 lines
Quoted 1 line
To fix the issue, we need to ensure the BPF JIT region is PMD size
aligned. This patch acchieve this goal by restoring the BPF JIT
region
Quoted 1 line
to original position, I.E the 128MB before kernel .text section.
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF" feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JITSo I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
To address "make sure modules and BPF programs get their own virtual regions", what about something as below (applied against this patch)?
arch/riscv/include/asm/pgtable.h +2
-2@@ -31,7 +31,7 @@ #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start)) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) #define BPF_JIT_REGION_END (VMALLOC_END)@@ -40,7 +40,7 @@ /* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END) #endifQuoted 24 lines
Again, good catch, thanks,
Alex
Quoted 6 lines
Quoted 1 line
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>---
arch/riscv/include/asm/pgtable.h| 5 ++---1 file changed, 2 insertions(+), 3 deletions(-)Review
Quoted 1 line
(quoted diff) +0
-0
b/arch/riscv/include/asm/pgtable.harch/riscv/include/asm/pgtable.h line 34
Quoted 9 lines
index
9469f464e71a..380cd3a7e548100644arch/riscv/include/asm/pgtable.h +0
-3@@ -30,9 +30,8 @@ > #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START +
BPF_JIT_REGION_SIZE)Quoted 1 line
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_START (BPF_JIT_REGION_END -Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
BPF_JIT_REGION_SIZE)Quoted 5 lines
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_END (MODULES_END) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) #define BPF_JIT_REGION_END (VMALLOC_END)This, when applied onto fixes, is breaking early boot on KASAN configurations for me.
Quoted 8 lines
Not surprising, I took a shortcut when initializing KASAN for modules, kernel and BPF:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR), kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));The kernel is then not covered, I'm taking a look at how to fix that properly.
The following based on "riscv: Introduce structure that group all variables regarding kernel mapping" fixes the issue:
arch/riscv/mm/kasan_init.c +0 -0
@@ -199,9 +199,12 @@ void __init kasan_init(void) kasan_populate(kasan_mem_to_shadow(start),
kasan_mem_to_shadow(end));
}- /* Populate kernel, BPF, modules mapping */
+ /* Populate BPF and modules mapping: modules mapping encompasses BPF mapping */
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
- kasan_mem_to_shadow((const void *)BPF_JIT_REGION_END));
+ kasan_mem_to_shadow((const void *)MODULES_END));
+ /* Populate kernel mapping */
+ kasan_populate(kasan_mem_to_shadow((const void *)kernel_map.virt_addr),
+ kasan_mem_to_shadow((const void *)kernel_map.virt_addr + kernel_map.size));
Without the mentioned patch, replace kernel_map.virt_addr with kernel_virt_addr and kernel_map.size with load_sz. Note that load_sz was re-exposed in v6 of the patchset "Map the kernel with correct permissions the first time".
Alex
Quoted 10 lines
Quoted 5 lines
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Re: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Quoted 161 lines · On Thu, 17 Jun 2021 16:18:54 +0200 Alex Ghiti <[email protected]> wrote:
Le 17/06/2021 à 10:09, Alex Ghiti a écrit :
Quoted 160 lines
Le 17/06/2021 à 09:30, Palmer Dabbelt a écrit :
Quoted 159 lines
Quoted 147 lines · On Tue, 15 Jun 2021 17:03:28 PDT (-0700), [email protected] wrote:
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 63 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 2 lines
From: Jisheng Zhang <[email protected]>
Quoted 1 line
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoidbreaking W^X")
Quoted 1 line
breaks booting with one kind of config file, I reproduced a kernel
panic
Quoted 2 lines
with the config:
Quoted 1 line
[ 0.138553] Unable to handle kernel paging request at virtual
address
ffffffff81201220Quoted 3 lines
[ 0.139159] Oops [#1]
[ 0.139303] Modules linked in:
[ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted5.13.0-rc5-default+ #1
Quoted 4 lines
[ 0.139934] Hardware name: riscv-virtio,qemu (DT)
[ 0.140193] epc :__memset+0xc4/0xfc
[ 0.140416] ra :skb_flow_dissector_init+0x1e/0x82[ 0.140609] epc :ffffffff8029806cra :ffffffff8033be78sp :
ffffffe001647da0Quoted 1 line
[ 0.140878] gp :
ffffffff81134b08tp :ffffffe001654380t0 :
ffffffff81201158Quoted 1 line
[ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 :
ffffffe001647dd0Quoted 1 line
[ 0.141424] s1 :
ffffffff80a43250a0 :ffffffff81201220a1 :0000000000000000
Quoted 1 line
[ 0.141654] a2 :
000000000000003ca3 :ffffffff81201258a4 :0000000000000064
Quoted 1 line
[ 0.141893] a5 :
ffffffff8029806ca6 : 0000000000000040 a7 :ffffffffffffffff
Quoted 1 line
[ 0.142126] s2 :
ffffffff81201220s3 : 0000000000000009 s4 :
ffffffff81135088Quoted 1 line
[ 0.142353] s5 :
ffffffff81135038s6 :ffffffff8080ce80s7 :
ffffffff80800438Quoted 1 line
[ 0.142584] s8 :
ffffffff80bc6578s9 : 0000000000000008 s10:
ffffffff806000acQuoted 1 line
[ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 :
0000000000000000
Quoted 2 lines
[ 0.143042] t5 : 0000000000000155 t6 :
00000000000003ff[ 0.143220] status: 0000000000000120 badaddr:ffffffff81201220cause:
000000000000000fQuoted 2 lines
[ 0.143560] [<
ffffffff8029806c>]__memset+0xc4/0xfc[ 0.143859] [<ffffffff8061e984>]init_default_flow_dissectors+0x22/0x60 > [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 > [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 > [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 > [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xcQuoted 6 lines
[ 0.145124] ---[ end trace
f1e9643daa46d591]---Quoted 1 line
After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 1 line
The
&_endis unlikely aligned with PMD size, so the front bpf jitregion sits with part of kernel .data section in one PMD size
mapping.
Quoted 2 lines
But kernel is mapped in PMD SIZE, when
bpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part ofkernel
Quoted 2 lines
.data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.
Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 1 line
Quoted 1 line
To fix the issue, we need to ensure the BPF JIT region is PMD size
Quoted 8 lines
Quoted 1 line
aligned. This patch acchieve this goal by restoring the BPF JIT
region
Quoted 1 line
to original position, I.E the 128MB before kernel .text section.
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but
IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF"
feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JITSo I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
To address "make sure modules and BPF programs get their own virtual regions",
what about something as below (applied against this patch)?arch/riscv/include/asm/pgtable.h +1
-1@@ -31,7 +31,7 @@ #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start)) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (
VMALLOC_END)arch/riscv/include/asm/pgtable.h +1
-1@@ -40,7 +40,7 @@ /* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END) #endifQuoted 23 lines
Again, good catch, thanks,
Alex
Quoted 6 lines
Quoted 1 line
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>---
arch/riscv/include/asm/pgtable.h| 5 ++---1 file changed, 2 insertions(+), 3 deletions(-)Review
Quoted 1 line
(quoted diff) +0
-0
b/arch/riscv/include/asm/pgtable.harch/riscv/include/asm/pgtable.h line 34
Quoted 9 lines
index
9469f464e71a..380cd3a7e548100644arch/riscv/include/asm/pgtable.h +0
-3@@ -30,9 +30,8 @@ > #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START +
BPF_JIT_REGION_SIZE)Quoted 7 lines
Quoted 7 lines
arch/riscv/include/asm/pgtable.h line 32
Quoted 1 line
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_START (BPF_JIT_REGION_END -
BPF_JIT_REGION_SIZE)Quoted 5 lines
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_END (MODULES_END) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) #define BPF_JIT_REGION_END (VMALLOC_END)This, when applied onto fixes, is breaking early boot on KASAN configurations for me.
I can reproduce this issue.
Quoted 33 lines
Quoted 11 lines
Not surprising, I took a shortcut when initializing KASAN for modules, kernel and BPF:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR), kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));The kernel is then not covered, I'm taking a look at how to fix that properly.
The following based on "riscv: Introduce structure that group all variables regarding kernel mapping" fixes the issue:
arch/riscv/mm/kasan_init.c +1
-1@@ -199,9 +199,12 @@ void __init kasan_init(void)kasan_populate (kasan_mem_to_shadow (start),kasan_mem_to_shadow (end)); } -/* Populate kernel, BPF, modules mapping */ +/* Populate BPF and modules mapping: modules mapping encompasses BPF mapping */
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
- kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));arch/riscv/mm/kasan_init.c +3
-0+ kasan_mem_to_shadow((const void *)MODULES_END)); +/* Populate kernel mapping */ + kasan_populate(kasan_mem_to_shadow((const void
Quoted 4 lines
*)kernel_map.virt_addr),
+ kasan_mem_to_shadow((const void
*)kernel_map.virt_addr + kernel_map.size));
If this patch works, maybe we can still use one kasan_populate() to cover kernel, bpf, and module:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
- kasan_mem_to_shadow((const void *)BPF_JIT_REGION_END));
+ kasan_mem_to_shadow((const void *)MODULES_VADDR + SZ_2G));
However, both can't solve the early boot hang issue. I'm not sure what's missing.
I applied your patch on rc6 + solution below "replace kernel_map.virt_addr with kernel_virt_addr and kernel_map.size with load_sz"
Thanks
Quoted 6 lines
Without the mentioned patch, replace kernel_map.virt_addr with
kernel_virt_addrand kernel_map.size withload_sz. Note thatload_szwas re-exposed in v6 of the patchset "Map the kernel with correct permissions the first time".
Re: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Quoted 209 lines · On Fri, 18 Jun 2021 01:27:31 +0800 Jisheng Zhang <[email protected]>…
Quoted 161 lines · On Thu, 17 Jun 2021 16:18:54 +0200 Alex Ghiti <[email protected]> wrote:
Le 17/06/2021 à 10:09, Alex Ghiti a écrit :
Quoted 160 lines
Le 17/06/2021 à 09:30, Palmer Dabbelt a écrit :
Quoted 159 lines
Quoted 147 lines · On Tue, 15 Jun 2021 17:03:28 PDT (-0700), [email protected] wrote:
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 63 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 2 lines
From: Jisheng Zhang <[email protected]>
Quoted 1 line
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoidbreaking W^X")
Quoted 1 line
breaks booting with one kind of config file, I reproduced a kernel
panic
Quoted 2 lines
with the config:
Quoted 1 line
[ 0.138553] Unable to handle kernel paging request at virtual
address
ffffffff81201220Quoted 3 lines
[ 0.139159] Oops [#1]
[ 0.139303] Modules linked in:
[ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted5.13.0-rc5-default+ #1
Quoted 4 lines
[ 0.139934] Hardware name: riscv-virtio,qemu (DT)
[ 0.140193] epc :__memset+0xc4/0xfc
[ 0.140416] ra :skb_flow_dissector_init+0x1e/0x82[ 0.140609] epc :ffffffff8029806cra :ffffffff8033be78sp :
ffffffe001647da0Quoted 1 line
[ 0.140878] gp :
ffffffff81134b08tp :ffffffe001654380t0 :
ffffffff81201158Quoted 1 line
[ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 :
ffffffe001647dd0Quoted 1 line
[ 0.141424] s1 :
ffffffff80a43250a0 :ffffffff81201220a1 :0000000000000000
Quoted 1 line
[ 0.141654] a2 :
000000000000003ca3 :ffffffff81201258a4 :0000000000000064
Quoted 1 line
[ 0.141893] a5 :
ffffffff8029806ca6 : 0000000000000040 a7 :ffffffffffffffff
Quoted 1 line
[ 0.142126] s2 :
ffffffff81201220s3 : 0000000000000009 s4 :
ffffffff81135088Quoted 1 line
[ 0.142353] s5 :
ffffffff81135038s6 :ffffffff8080ce80s7 :
ffffffff80800438Quoted 1 line
[ 0.142584] s8 :
ffffffff80bc6578s9 : 0000000000000008 s10:
ffffffff806000acQuoted 1 line
[ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 :
0000000000000000
Quoted 2 lines
[ 0.143042] t5 : 0000000000000155 t6 :
00000000000003ff[ 0.143220] status: 0000000000000120 badaddr:ffffffff81201220cause:
000000000000000fQuoted 2 lines
[ 0.143560] [<
ffffffff8029806c>]__memset+0xc4/0xfc[ 0.143859] [<ffffffff8061e984>]init_default_flow_dissectors+0x22/0x60 > [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 > [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 > [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 > [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xcQuoted 6 lines
[ 0.145124] ---[ end trace
f1e9643daa46d591]---Quoted 1 line
After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 1 line
The
&_endis unlikely aligned with PMD size, so the front bpf jitregion sits with part of kernel .data section in one PMD size
mapping.
Quoted 2 lines
But kernel is mapped in PMD SIZE, when
bpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part ofkernel
Quoted 2 lines
.data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.
Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 1 line
Quoted 1 line
To fix the issue, we need to ensure the BPF JIT region is PMD size
Quoted 8 lines
Quoted 1 line
aligned. This patch acchieve this goal by restoring the BPF JIT
region
Quoted 1 line
to original position, I.E the 128MB before kernel .text section.
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but
IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF"
feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JITSo I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
To address "make sure modules and BPF programs get their own virtual regions",
what about something as below (applied against this patch)?arch/riscv/include/asm/pgtable.h +1
-1@@ -31,7 +31,7 @@ #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start)) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (
VMALLOC_END)arch/riscv/include/asm/pgtable.h +1
-1@@ -40,7 +40,7 @@ /* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END) #endifQuoted 23 lines
Again, good catch, thanks,
Alex
Quoted 6 lines
Quoted 1 line
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>---
arch/riscv/include/asm/pgtable.h| 5 ++---1 file changed, 2 insertions(+), 3 deletions(-)Review
Quoted 1 line
(quoted diff) +0
-0
b/arch/riscv/include/asm/pgtable.harch/riscv/include/asm/pgtable.h line 34
Quoted 9 lines
index
9469f464e71a..380cd3a7e548100644arch/riscv/include/asm/pgtable.h +0
-3@@ -30,9 +30,8 @@ > #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START +
BPF_JIT_REGION_SIZE)Quoted 7 lines
Quoted 7 lines
arch/riscv/include/asm/pgtable.h line 32
Quoted 1 line
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_START (BPF_JIT_REGION_END -
BPF_JIT_REGION_SIZE)Quoted 5 lines
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_END (MODULES_END) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) #define BPF_JIT_REGION_END (VMALLOC_END)This, when applied onto fixes, is breaking early boot on KASAN configurations for me.
I can reproduce this issue.
Quoted 33 lines
Quoted 11 lines
Not surprising, I took a shortcut when initializing KASAN for modules, kernel and BPF:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR), kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));The kernel is then not covered, I'm taking a look at how to fix that properly.
The following based on "riscv: Introduce structure that group all variables regarding kernel mapping" fixes the issue:
arch/riscv/mm/kasan_init.c +1
-1@@ -199,9 +199,12 @@ void __init kasan_init(void)kasan_populate (kasan_mem_to_shadow (start),kasan_mem_to_shadow (end)); } -/* Populate kernel, BPF, modules mapping */ +/* Populate BPF and modules mapping: modules mapping encompasses BPF mapping */
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
- kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));arch/riscv/mm/kasan_init.c +3
-0+ kasan_mem_to_shadow((const void *)MODULES_END)); +/* Populate kernel mapping */ + kasan_populate(kasan_mem_to_shadow((const voidQuoted 4 lines
*)kernel_map.virt_addr),
+ kasan_mem_to_shadow((const void
*)kernel_map.virt_addr + kernel_map.size));If this patch works, maybe we can still use one
kasan_populate()to cover kernel, bpf, and module:kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
Review
Quoted 2 lines
(quoted diff) +1
-1- kasan_mem_to_shadow((const void *)BPF_JIT_REGION_END)); + kasan_mem_to_shadow((const void *)MODULES_VADDR + SZ_2G));
I made a mistake. Below patch works:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
- kasan_mem_to_shadow((const void *)BPF_JIT_REGION_END));
+ kasan_mem_to_shadow((const void *)(MODULES_VADDR + SZ_2G)));
Quoted 20 lines
However, both can't solve the early boot hang issue. I'm not sure what's missing.
I applied your patch on rc6 + solution below "replace kernel_map.virt_addr with
kernel_virt_addrand kernel_map.size withload_sz"Thanks
Quoted 6 lines
Without the mentioned patch, replace kernel_map.virt_addr with
kernel_virt_addrand kernel_map.size withload_sz. Note thatload_szwas re-exposed in v6 of the patchset "Map the kernel with correct permissions the first time"._______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Re: [PATCH] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Quoted 218 lines · On Fri, 18 Jun 2021 01:46:48 +0800 Jisheng Zhang <[email protected]>…
Quoted 209 lines · On Fri, 18 Jun 2021 01:27:31 +0800 Jisheng Zhang <[email protected]>…
Quoted 161 lines · On Thu, 17 Jun 2021 16:18:54 +0200 Alex Ghiti <[email protected]> wrote:
Le 17/06/2021 à 10:09, Alex Ghiti a écrit :
Quoted 160 lines
Le 17/06/2021 à 09:30, Palmer Dabbelt a écrit :
Quoted 159 lines
Quoted 147 lines · On Tue, 15 Jun 2021 17:03:28 PDT (-0700), [email protected] wrote:
Quoted 1 line · On Tue, 15 Jun 2021 20:54:19 +0200 Alex Ghiti <[email protected]> wrote:
Hi Jisheng,
Hi Alex,
Quoted 63 lines
Le 14/06/2021 à 18:49, Jisheng Zhang a écrit :
Quoted 2 lines
From: Jisheng Zhang <[email protected]>
Quoted 1 line
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoidbreaking W^X")
Quoted 1 line
breaks booting with one kind of config file, I reproduced a kernel
panic
Quoted 2 lines
with the config:
Quoted 1 line
[ 0.138553] Unable to handle kernel paging request at virtual
address
ffffffff81201220Quoted 3 lines
[ 0.139159] Oops [#1]
[ 0.139303] Modules linked in:
[ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted5.13.0-rc5-default+ #1
Quoted 4 lines
[ 0.139934] Hardware name: riscv-virtio,qemu (DT)
[ 0.140193] epc :__memset+0xc4/0xfc
[ 0.140416] ra :skb_flow_dissector_init+0x1e/0x82[ 0.140609] epc :ffffffff8029806cra :ffffffff8033be78sp :
ffffffe001647da0Quoted 1 line
[ 0.140878] gp :
ffffffff81134b08tp :ffffffe001654380t0 :
ffffffff81201158Quoted 1 line
[ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 :
ffffffe001647dd0Quoted 1 line
[ 0.141424] s1 :
ffffffff80a43250a0 :ffffffff81201220a1 :0000000000000000
Quoted 1 line
[ 0.141654] a2 :
000000000000003ca3 :ffffffff81201258a4 :0000000000000064
Quoted 1 line
[ 0.141893] a5 :
ffffffff8029806ca6 : 0000000000000040 a7 :ffffffffffffffff
Quoted 1 line
[ 0.142126] s2 :
ffffffff81201220s3 : 0000000000000009 s4 :
ffffffff81135088Quoted 1 line
[ 0.142353] s5 :
ffffffff81135038s6 :ffffffff8080ce80s7 :
ffffffff80800438Quoted 1 line
[ 0.142584] s8 :
ffffffff80bc6578s9 : 0000000000000008 s10:
ffffffff806000acQuoted 1 line
[ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 :
0000000000000000
Quoted 2 lines
[ 0.143042] t5 : 0000000000000155 t6 :
00000000000003ff[ 0.143220] status: 0000000000000120 badaddr:ffffffff81201220cause:
000000000000000fQuoted 2 lines
[ 0.143560] [<
ffffffff8029806c>]__memset+0xc4/0xfc[ 0.143859] [<ffffffff8061e984>]init_default_flow_dissectors+0x22/0x60 > [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 > [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 > [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 > [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xcQuoted 6 lines
[ 0.145124] ---[ end trace
f1e9643daa46d591]---Quoted 1 line
After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:Quoted 1 line
The
&_endis unlikely aligned with PMD size, so the front bpf jitregion sits with part of kernel .data section in one PMD size
mapping.
Quoted 2 lines
But kernel is mapped in PMD SIZE, when
bpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part ofkernel
Quoted 2 lines
.data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.
Good catch, we make sure no physical allocation happens between
_endand the next PMD aligned address, but I missed this one.Quoted 1 line
Quoted 1 line
To fix the issue, we need to ensure the BPF JIT region is PMD size
Quoted 8 lines
Quoted 1 line
aligned. This patch acchieve this goal by restoring the BPF JIT
region
Quoted 1 line
to original position, I.E the 128MB before kernel .text section.
But I disagree with your solution: I made sure modules and BPF programs get their own virtual regions to avoid worst case scenario where one could allocate all the space and leave nothing to the other (we are limited to +- 2GB offset). Why don't just align
BPF_JIT_REGION_STARTto the next PMD aligned address?Originally, I planed to fix the issue by aligning
BPF_JIT_REGION_START, but
IIRC, BPF experts are adding (or have added) "Calling kernel functions from BPF"
feature, there's a risk that BPF JIT region is beyond the 2GB of module region:------
module
------
kernel
------BPF_JITSo I made this patch finally. In this patch, we let BPF JIT region sit between module and kernel.
To address "make sure modules and BPF programs get their own virtual regions",
what about something as below (applied against this patch)?arch/riscv/include/asm/pgtable.h +1
-1@@ -31,7 +31,7 @@ #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT #define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) -#define BPF_JIT_REGION_END (MODULES_END) +#define BPF_JIT_REGION_END (PFN_ALIGN((unsigned long)&_start)) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (
VMALLOC_END)arch/riscv/include/asm/pgtable.h +1
-1@@ -40,7 +40,7 @@ /* Modules always live before the kernel */ #ifdef CONFIG_64BIT #define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G) -#define MODULES_END (PFN_ALIGN((unsigned long)&_start)) +#define MODULES_END (BPF_JIT_REGION_END) #endifQuoted 23 lines
Again, good catch, thanks,
Alex
Quoted 6 lines
Quoted 1 line
Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>---
arch/riscv/include/asm/pgtable.h| 5 ++---1 file changed, 2 insertions(+), 3 deletions(-)Review
Quoted 1 line
(quoted diff) +0
-0
b/arch/riscv/include/asm/pgtable.harch/riscv/include/asm/pgtable.h line 34
Quoted 9 lines
index
9469f464e71a..380cd3a7e548100644arch/riscv/include/asm/pgtable.h +0
-3@@ -30,9 +30,8 @@ > #define BPF_JIT_REGION_SIZE (SZ_128M) #ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START +
BPF_JIT_REGION_SIZE)Quoted 7 lines
Quoted 7 lines
arch/riscv/include/asm/pgtable.h line 32
Quoted 1 line
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_START (BPF_JIT_REGION_END -
BPF_JIT_REGION_SIZE)Quoted 5 lines
arch/riscv/include/asm/pgtable.h +1
-0+#define BPF_JIT_REGION_END (MODULES_END) #else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) #define BPF_JIT_REGION_END (VMALLOC_END)This, when applied onto fixes, is breaking early boot on KASAN configurations for me.
I can reproduce this issue.
Quoted 33 lines
Quoted 11 lines
Not surprising, I took a shortcut when initializing KASAN for modules, kernel and BPF:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR), kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));The kernel is then not covered, I'm taking a look at how to fix that properly.
The following based on "riscv: Introduce structure that group all variables regarding kernel mapping" fixes the issue:
arch/riscv/mm/kasan_init.c +1
-1@@ -199,9 +199,12 @@ void __init kasan_init(void)kasan_populate (kasan_mem_to_shadow (start),kasan_mem_to_shadow (end)); } -/* Populate kernel, BPF, modules mapping */ +/* Populate BPF and modules mapping: modules mapping encompasses BPF mapping */
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
- kasan_mem_to_shadow((const void
*)BPF_JIT_REGION_END));arch/riscv/mm/kasan_init.c +3
-0+ kasan_mem_to_shadow((const void *)MODULES_END)); +/* Populate kernel mapping */ + kasan_populate(kasan_mem_to_shadow((const voidQuoted 4 lines
*)kernel_map.virt_addr),
+ kasan_mem_to_shadow((const void
*)kernel_map.virt_addr + kernel_map.size));If this patch works, maybe we can still use one
kasan_populate()to cover kernel, bpf, and module:kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
Review
Quoted 2 lines
(quoted diff) +1
-1- kasan_mem_to_shadow((const void *)BPF_JIT_REGION_END)); + kasan_mem_to_shadow((const void *)MODULES_VADDR + SZ_2G));I made a mistake. Below patch works:
kasan_populate(kasan_mem_to_shadow((const void *)MODULES_VADDR),
Review
Quoted 2 lines
(quoted diff) +1
-1- kasan_mem_to_shadow((const void *)BPF_JIT_REGION_END)); + kasan_mem_to_shadow((const void *)(MODULES_VADDR + SZ_2G)));
This isn't the key. I knew the reason now. kasan_init() has local vars named as _start and _end, then MODULES_VADDR is defined as:
#define MODULES_VADDR (PFN_ALIGN((unsigned long)&_end) - SZ_2G)
So MODULES_VADDR isn't what we expected. To fix it, we must rename the local vars
Quoted 22 lines
Quoted 21 lines
However, both can't solve the early boot hang issue. I'm not sure what's missing.
I applied your patch on rc6 + solution below "replace kernel_map.virt_addr with
kernel_virt_addrand kernel_map.size withload_sz"Thanks
Quoted 6 lines
Without the mentioned patch, replace kernel_map.virt_addr with
kernel_virt_addrand kernel_map.size withload_sz. Note thatload_szwas re-exposed in v6 of the patchset "Map the kernel with correct permissions the first time"._______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
PATCH v2 1/1 riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Andreas reported commit fc8504765ec5 ("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of defconfig, I reproduced a kernel panic with the defconfig:
[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---
After some investigation, I think I found the root cause: commit 2bfc6cd81bd ("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:
The &_end is unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, when bpf_jit_binary_lock_ro() is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.
To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section. The modification to kasan_init.c is inspired by Alexandre.
---
Since v1:
- Fix early boot hang when kasan is enabled
- Update Documentation/riscv/vm-layout.rst
Documentation/riscv/vm-layout.rst | 4 ++-- arch/riscv/include/asm/pgtable.h | 5 ++--- arch/riscv/mm/kasan_init.c | 10 +++++----- 3 files changed, 9 insertions(+), 10 deletions(-)
Documentation/riscv/vm-layout.rst +2 -2
@@ -58,6 +58,6 @@ RISC-V Linux Kernel SV39 | ____________________________________________________________|____________________________________________________________ | | | | - ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | modules - ffffffff80000000 | -2 GB | ffffffffffffffff | 2 GB | kernel, BPF + ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | modules, BPF + ffffffff80000000 | -2 GB | ffffffffffffffff | 2 GB | kernel __________________|____________|__________________|_________|____________________________________________________________
arch/riscv/include/asm/pgtable.h +2 -3
@@ -30,9 +30,8 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)
arch/riscv/mm/kasan_init.c +5 -5
@@ -169,7 +169,7 @@ static void __init kasan_shallow_populate(void *start, void *end)void __init kasan_init (void ) { -phys_addr_t _start, _end; +phys_addr_t p_start, p_end;u64 i;/*
@@ -189,9 +189,9 @@ void __init kasan_init(void) (void *)kasan_mem_to_shadow((void *)VMALLOC_END));/* Populate the linear mapping */ -for_each_mem_range (i, &_start, &_end) { -void *start = (void *)__va (_start); -void *end = (void *)__va (_end); +for_each_mem_range (i, &p_start, &p_end) { +void *start = (void *)__va (p_start); +void *end = (void *)__va (p_end);if (start >= end)break ;
@@ -201,7 +201,7 @@ void __init kasan_init(void)/* Populate kernel, BPF, modules mapping */ kasan_populate (kasan_mem_to_shadow ((const void *)MODULES_VADDR ), -kasan_mem_to_shadow ((const void *)BPF_JIT_REGION_END )); +kasan_mem_to_shadow ((const void *)MODULES_VADDR +SZ_2G ));for (i =0 ; i <PTRS_PER_PTE ; i++) set_pte(&kasan_early_shadow_pte[i],
Signature · 1 line
2.32.0
Alex Ghiti
reviewerRe: [PATCH v2] riscv: Ensure BPF_JIT_REGION_START aligned with PMD size
Le 17/06/2021 à 20:15, Jisheng Zhang a écrit :
Quoted 94 lines
Andreas reported commit
fc8504765ec5("riscv: bpf: Avoid breaking W^X") breaks booting with one kind of defconfig, I reproduced a kernel panic with the defconfig:[ 0.138553] Unable to handle kernel paging request at virtual address ffffffff81201220 [ 0.139159] Oops [#1] [ 0.139303] Modules linked in: [ 0.139601] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-rc5-default+ #1 [ 0.139934] Hardware name: riscv-virtio,qemu (DT) [ 0.140193] epc : __memset+0xc4/0xfc [ 0.140416] ra : skb_flow_dissector_init+0x1e/0x82 [ 0.140609] epc : ffffffff8029806c ra : ffffffff8033be78 sp : ffffffe001647da0 [ 0.140878] gp : ffffffff81134b08 tp : ffffffe001654380 t0 : ffffffff81201158 [ 0.141156] t1 : 0000000000000002 t2 : 0000000000000154 s0 : ffffffe001647dd0 [ 0.141424] s1 : ffffffff80a43250 a0 : ffffffff81201220 a1 : 0000000000000000 [ 0.141654] a2 : 000000000000003c a3 : ffffffff81201258 a4 : 0000000000000064 [ 0.141893] a5 : ffffffff8029806c a6 : 0000000000000040 a7 : ffffffffffffffff [ 0.142126] s2 : ffffffff81201220 s3 : 0000000000000009 s4 : ffffffff81135088 [ 0.142353] s5 : ffffffff81135038 s6 : ffffffff8080ce80 s7 : ffffffff80800438 [ 0.142584] s8 : ffffffff80bc6578 s9 : 0000000000000008 s10: ffffffff806000ac [ 0.142810] s11: 0000000000000000 t3 : fffffffffffffffc t4 : 0000000000000000 [ 0.143042] t5 : 0000000000000155 t6 : 00000000000003ff [ 0.143220] status: 0000000000000120 badaddr: ffffffff81201220 cause: 000000000000000f [ 0.143560] [<ffffffff8029806c>] __memset+0xc4/0xfc [ 0.143859] [<ffffffff8061e984>] init_default_flow_dissectors+0x22/0x60 [ 0.144092] [<ffffffff800010fc>] do_one_initcall+0x3e/0x168 [ 0.144278] [<ffffffff80600df0>] kernel_init_freeable+0x1c8/0x224 [ 0.144479] [<ffffffff804868a8>] kernel_init+0x12/0x110 [ 0.144658] [<ffffffff800022de>] ret_from_exception+0x0/0xc [ 0.145124] ---[ end trace f1e9643daa46d591 ]---After some investigation, I think I found the root cause: commit
2bfc6cd81bd("move kernel mapping outside of linear mapping") moves BPF JIT region after the kernel:The
&_endis unlikely aligned with PMD size, so the front bpf jit region sits with part of kernel .data section in one PMD size mapping. But kernel is mapped in PMD SIZE, whenbpf_jit_binary_lock_ro()is called to make the first bpf jit prog ROX, we will make part of kernel .data section RO too, so when we write to, for example memset the .data section, MMU will trigger a store page fault.To fix the issue, we need to ensure the BPF JIT region is PMD size aligned. This patch acchieve this goal by restoring the BPF JIT region to original position, I.E the 128MB before kernel .text section. The modification to
kasan_init.cis inspired by Alexandre.Reported-by Andreas Schwab <[email protected]>Signed-off-by Jisheng Zhang <[email protected]>---
Since v1:
- Fix early boot hang when kasan is enabled
- UpdateDocumentation/riscv/vm-layout.rstDocumentation/riscv/vm-layout.rst | 4 ++-- arch/riscv/include/asm/pgtable.h | 5 ++--- arch/riscv/mm/kasan_init.c | 10 +++++----- 3 files changed, 9 insertions(+), 10 deletions(-)Documentation/riscv/vm-layout.rst +2
-2@@ -58,6 +58,6 @@ RISC-V Linux Kernel SV39 | ____________________________________________________________|____________________________________________________________ | | | | - ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | modules - ffffffff80000000 | -2 GB | ffffffffffffffff | 2 GB | kernel, BPF + ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | modules, BPF + ffffffff80000000 | -2 GB | ffffffffffffffff | 2 GB | kernel __________________|____________|__________________|_________|____________________________________________________________arch/riscv/include/asm/pgtable.h +2
-3@@ -30,9 +30,8 @@#define BPF_JIT_REGION_SIZE (SZ_128M)#ifdef CONFIG_64BIT -/* KASLR should leave at least 128MB for BPF after the kernel */ -#define BPF_JIT_REGION_START PFN_ALIGN((unsigned long)&_end) -#define BPF_JIT_REGION_END (BPF_JIT_REGION_START + BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_START (BPF_JIT_REGION_END - BPF_JIT_REGION_SIZE) +#define BPF_JIT_REGION_END (MODULES_END)#else #define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE)#define BPF_JIT_REGION_END (VMALLOC_END)arch/riscv/mm/kasan_init.c +0
-0
arch/riscv/mm/kasan_init.c static void __init kasan_shallow_populate(void *start, void *end) · line 172
Quoted 5 lines
arch/riscv/mm/kasan_init.c +1
-1@@ -169,7 +169,7 @@ static void __init kasan_shallow_populate(void *start, void *end)void __init kasan_init (void ) { -phys_addr_t _start, _end; +phys_addr_t p_start, p_end;
IMHO this fix deserves its own patch, it is not related to the issue you describe in the changelog and has been around for some time.
That's too bad BPF people did not answer my question regarding BPF <-> modules calls: I'll ask the question directly in kasan-dev mailing list and add you in cc.
Quoted 26 lines
arch/riscv/mm/kasan_init.c +4
-4u64 i;/* @@ -189,9 +189,9 @@ void __init kasan_init(void) (void *)kasan_mem_to_shadow((void *)VMALLOC_END));/* Populate the linear mapping */ -for_each_mem_range (i, &_start, &_end) { -void *start = (void *)__va (_start); -void *end = (void *)__va (_end); +for_each_mem_range (i, &p_start, &p_end) { +void *start = (void *)__va (p_start); +void *end = (void *)__va (p_end);if (start >= end)break ;@@ -201,7 +201,7 @@ void __init kasan_init(void)/* Populate kernel, BPF, modules mapping */ kasan_populate (kasan_mem_to_shadow ((const void *)MODULES_VADDR ), -kasan_mem_to_shadow ((const void *)BPF_JIT_REGION_END )); +kasan_mem_to_shadow ((const void *)MODULES_VADDR +SZ_2G ));for (i =0 ; i <PTRS_PER_PTE ; i++) set_pte(&kasan_early_shadow_pte[i],
PATCH 8/9 riscv: module: Create module allocations without exec permissions
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
The core code manages the executable permissions of code regions of modules explicitly, it is not necessary to create the module vmalloc regions with RWX permissions. Create them with RW- permissions instead.
--- arch/riscv/kernel/module.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/riscv/kernel/module.c +1 -1
@@ -414,7 +414,7 @@ void *module_alloc(unsigned long size) {return __vmalloc_node_range (size,1 ,VMALLOC_MODULE_START ,VMALLOC_END ,GFP_KERNEL , -PAGE_KERNEL_EXEC ,0 ,NUMA_NO_NODE , +PAGE_KERNEL ,0 ,NUMA_NO_NODE ,__builtin_return_address (0 )); }#endif
Signature · 1 line
2.31.0
PATCH 9/9 riscv: Set ARCH_HAS_STRICT_MODULE_RWX if MMU
In reply to Jisheng ZhangFrom: Jisheng Zhang <[email protected]>
Now we can set ARCH_HAS_STRICT_MODULE_RWX for MMU riscv platforms, this is good from security perspective.
--- arch/riscv/Kconfig | 1 + 1 file changed, 1 insertion(+)
arch/riscv/Kconfig +1 -0
@@ -28,6 +28,7 @@ config RISCV select ARCH_HAS_SET_DIRECT_MAP select ARCH_HAS_SET_MEMORY select ARCH_HAS_STRICT_KERNEL_RWX if MMU + select ARCH_HAS_STRICT_MODULE_RWX if MMU select ARCH_OPTIONAL_KERNEL_RWX if ARCH_HAS_STRICT_KERNEL_RWX select ARCH_OPTIONAL_KERNEL_RWX_DEFAULT select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT if MMU
Signature · 1 line
2.31.0
Palmer Dabbelt
maintainerQuoted 31 lines · On Mon, 29 Mar 2021 11:21:44 PDT (-0700), [email protected] wrote:
From: Jisheng Zhang <[email protected]>
patch1 is a trivial improvement patch to move some functions to .init section
Then following patches improve self-protection by:
Marking some variables
__ro_after_init
Constifing some variables
EnablingARCH_HAS_STRICT_MODULE_RWXJisheng Zhang (9):
riscv: add__initsection marker to some functions
riscv: Mark some global variables__ro_after_init
riscv: Constifysys_call_table
riscv: Constifysbi_ipi_ops
riscv: kprobes: Implementalloc_insn_page()
riscv: bpf: Movebpf_jit_alloc_exec()andbpf_jit_free_exec()to core
riscv: bpf: Avoid breaking W^X
riscv: module: Create module allocations without exec permissions
riscv: SetARCH_HAS_STRICT_MODULE_RWXif MMUarch/riscv/Kconfig | 1 + arch/riscv/include/asm/smp.h | 4 ++-- arch/riscv/include/asm/syscall.h | 2 +- arch/riscv/kernel/module.c | 2 +- arch/riscv/kernel/probes/kprobes.c | 8 ++++++++ arch/riscv/kernel/sbi.c | 10 +++++----- arch/riscv/kernel/smp.c | 6 +++--- arch/riscv/kernel/syscall_table.c | 2 +- arch/riscv/kernel/time.c | 2 +-
Quoted 8 lines
arch/riscv/kernel/traps.c | 2 +- arch/riscv/kernel/vdso.c | 4 ++-- arch/riscv/mm/init.c | 12 ++++++------ arch/riscv/mm/kasan_init.c | 6 +++--- arch/riscv/mm/ptdump.c | 2 +- arch/riscv/net/bpf_jit_comp64.c | 13 ------------- arch/riscv/net/bpf_jit_core.c | 14 ++++++++++++++ 16 files changed, 50 insertions(+), 40 deletions(-)
Thanks. These are on for-next. I had to fix up a handful of merge conflicts, so LMK if I made any mistakes.
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv