summaryrefslogtreecommitdiffstats
path: root/drivers/memory/mtk-smi.c
diff options
context:
space:
mode:
authorAtish Patra <atish.patra@wdc.com>2020-11-04 16:04:38 -0800
committerPalmer Dabbelt <palmerdabbelt@google.com>2020-11-25 16:05:28 -0800
commit19a00869028f4a28a36f90649166631dff6e3ccd (patch)
treeef4a68e11c94a44d7e9de3f6f83fe57877739ba9 /drivers/memory/mtk-smi.c
parentb6566dc1acca38ce6ed845ce8a270fb181ff6d41 (diff)
downloadlinux-19a00869028f4a28a36f90649166631dff6e3ccd.tar.bz2
RISC-V: Protect all kernel sections including init early
Currently, .init.text & .init.data are intermixed which makes it impossible apply different permissions to them. .init.data shouldn't need exec permissions while .init.text shouldn't have write permission. Moreover, the strict permission are only enforced /init starts. This leaves the kernel vulnerable from possible buggy built-in modules. Keep .init.text & .data in separate sections so that different permissions are applied to each section. Apply permissions to individual sections as early as possible. This improves the kernel protection under CONFIG_STRICT_KERNEL_RWX. We also need to restore the permissions for the entire _init section after it is freed so that those pages can be used for other purpose. Signed-off-by: Atish Patra <atish.patra@wdc.com> Tested-by: Greentime Hu <greentime.hu@sifive.com> Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
Diffstat (limited to 'drivers/memory/mtk-smi.c')
0 files changed, 0 insertions, 0 deletions