LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, marc.zyngier@arm.com,
mark.rutland@arm.com, linux-kernel@vger.kernel.org,
Nadav Amit <namit@vmware.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
James Morse <james.morse@arm.com>
Subject: Re: [PATCH 0/4] arm64: wire up VM_FLUSH_RESET_PERMS
Date: Tue, 28 May 2019 12:29:21 +0200 [thread overview]
Message-ID: <8963e2ba-be92-39cb-40f1-7df89aa1e635@arm.com> (raw)
In-Reply-To: <20190528100413.GA20809@fuggles.cambridge.arm.com>
On 5/28/19 12:04 PM, Will Deacon wrote:
> On Thu, May 23, 2019 at 11:22:52AM +0100, Ard Biesheuvel wrote:
>> 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@vmware.com>
>> Cc: Rick Edgecombe <rick.p.edgecombe@intel.com>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Will Deacon <will.deacon@arm.com>
>> Cc: Masami Hiramatsu <mhiramat@kernel.org>
>> Cc: James Morse <james.morse@arm.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(-)
>
> Thanks, this all looks good to me. I can get pick this up for 5.2 if
> Rick's fixes [1] land soon enough.
>
Note that you'll get a trivial conflict in the hunk against mm/vmalloc.c.
next prev parent reply other threads:[~2019-05-28 10:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 10:22 [PATCH 0/4] arm64: wire up VM_FLUSH_RESET_PERMS Ard Biesheuvel
2019-05-23 10:22 ` [PATCH 1/4] arm64: module: create module allocations without exec permissions Ard Biesheuvel
2019-05-28 5:35 ` Anshuman Khandual
2019-05-28 6:24 ` Ard Biesheuvel
2019-05-23 10:22 ` [PATCH 2/4] arm64/mm: wire up CONFIG_ARCH_HAS_SET_DIRECT_MAP Ard Biesheuvel
2019-05-28 8:10 ` Anshuman Khandual
2019-05-28 8:20 ` Ard Biesheuvel
2019-05-28 8:41 ` Anshuman Khandual
2019-05-28 8:58 ` Ard Biesheuvel
2019-05-23 10:22 ` [PATCH 3/4] arm64/kprobes: set VM_FLUSH_RESET_PERMS on kprobe instruction pages Ard Biesheuvel
2019-05-28 8:20 ` Anshuman Khandual
2019-05-28 8:23 ` Ard Biesheuvel
2019-05-23 10:22 ` [PATCH 4/4] arm64: bpf: do not allocate executable memory Ard Biesheuvel
2019-05-28 10:04 ` [PATCH 0/4] arm64: wire up VM_FLUSH_RESET_PERMS Will Deacon
2019-05-28 10:29 ` Ard Biesheuvel [this message]
2019-06-24 11:16 ` Will Deacon
2019-06-24 11:22 ` Ard Biesheuvel
2019-06-24 14:29 ` Ard Biesheuvel
2019-06-24 17:14 ` Catalin Marinas
2019-06-24 17:15 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8963e2ba-be92-39cb-40f1-7df89aa1e635@arm.com \
--to=ard.biesheuvel@arm.com \
--cc=akpm@linux-foundation.org \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).