[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190523102256.29168-1-ard.biesheuvel@arm.com>
Date: Thu, 23 May 2019 11:22:52 +0100
From: Ard Biesheuvel <ard.biesheuvel@....com>
To: linux-arm-kernel@...ts.infradead.org
Cc: marc.zyngier@....com, mark.rutland@....com,
linux-kernel@...r.kernel.org,
Ard Biesheuvel <ard.biesheuvel@....com>,
Nadav Amit <namit@...are.com>,
Rick Edgecombe <rick.p.edgecombe@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Will Deacon <will.deacon@....com>,
Masami Hiramatsu <mhiramat@...nel.org>,
James Morse <james.morse@....com>
Subject: [PATCH 0/4] arm64: wire up VM_FLUSH_RESET_PERMS
Wire up the code introduced in v5.2 to manage the permissions
of executable vmalloc regions (and their linear aliases) more
strictly.
One of the things that came up in the internal discussion is
whether non-x86 architectures have any benefit at all from the
lazy vunmap feature, and whether it would perhaps be better to
implement eager vunmap instead.
Cc: Nadav Amit <namit@...are.com>
Cc: Rick Edgecombe <rick.p.edgecombe@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: Will Deacon <will.deacon@....com>
Cc: Masami Hiramatsu <mhiramat@...nel.org>
Cc: James Morse <james.morse@....com>
Ard Biesheuvel (4):
arm64: module: create module allocations without exec permissions
arm64/mm: wire up CONFIG_ARCH_HAS_SET_DIRECT_MAP
arm64/kprobes: set VM_FLUSH_RESET_PERMS on kprobe instruction pages
arm64: bpf: do not allocate executable memory
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/cacheflush.h | 3 ++
arch/arm64/kernel/module.c | 4 +-
arch/arm64/kernel/probes/kprobes.c | 4 +-
arch/arm64/mm/pageattr.c | 48 ++++++++++++++++----
arch/arm64/net/bpf_jit_comp.c | 2 +-
mm/vmalloc.c | 11 -----
7 files changed, 50 insertions(+), 23 deletions(-)
--
2.17.1
Powered by blists - more mailing lists