[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160113000112.GA36310@ast-mbp.thefacebook.com>
Date: Tue, 12 Jan 2016 16:01:13 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Laura Abbott <labbott@...oraproject.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Mark Rutland <mark.rutland@....com>,
Kees Cook <keescook@...omium.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: Allow vmalloc regions to be set with set_memory_*
On Tue, Jan 12, 2016 at 01:46:27PM -0800, Laura Abbott 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.
>
> Signed-off-by: Laura Abbott <labbott@...oraproject.org>
> ---
> This should let the protections for the eBPF work as expected, I don't
> know if there is some sort of self test for thatL.
you can test it with:
# sysctl net.core.bpf_jit_enable=1
# insmod test_bpf.ko
On x64 it shows:
test_bpf: Summary: 291 PASSED, 0 FAILED, [282/283 JIT'ed]
arm64 may have less JIT'ed tests.
Powered by blists - more mailing lists