[PATCH] arm64: allow vmalloc regions to be set with set_memory_*

Ard Biesheuvel ard.biesheuvel at linaro.org
Thu Jan 28 08:40:23 PST 2016

On 28 January 2016 at 16:08, Will Deacon <will.deacon at arm.com> wrote:
> On Mon, Jan 18, 2016 at 03:01:05PM +0100, Ard Biesheuvel wrote:
>> The range of set_memory_* is currently restricted to the module address
>> range because of difficulties in breaking down larger block sizes.
>> vmalloc maps PAGE_SIZE pages so it is safe to use as well. Update the
>> function ranges and add a comment explaining why the range is restricted
>> the way it is.
>> Suggested-by: Laura Abbott <labbott at fedoraproject.org>
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel at linaro.org>
>> ---
>>  arch/arm64/mm/pageattr.c | 23 +++++++++++++++++++----
>>  1 file changed, 19 insertions(+), 4 deletions(-)
> What's the user for this? It would be better to apply along with something
> that actually needs to change permission for arbitrary vmalloc mappings.

BPF already uses set_memory_ro() but doesn't bother to check the return value.

Before the patch, I get:

> Anyway, with that (and a rebase to -rc2):
> Acked-by: Will Deacon <will.deacon at arm.com>
> Will

More information about the linux-arm-kernel mailing list