summaryrefslogtreecommitdiffstats
path: root/lib/test_bpf.c
diff options
context:
space:
mode:
authorTong Tiangen <tongtiangen@huawei.com>2021-10-27 13:18:22 +0200
committerDaniel Borkmann <daniel@iogearbox.net>2021-10-28 01:02:44 +0200
commit252c765bd764a246a8bd516fabf6d6123df4a24f (patch)
tree47ba312f3ec4698cd0829237b01d3f2bbc5ee492 /lib/test_bpf.c
parentMerge branch 'selftests/bpf: parallel mode improvement' (diff)
downloadlinux-252c765bd764a246a8bd516fabf6d6123df4a24f.tar.xz
linux-252c765bd764a246a8bd516fabf6d6123df4a24f.zip
riscv, bpf: Add BPF exception tables
When a tracing BPF program attempts to read memory without using the bpf_probe_read() helper, the verifier marks the load instruction with the BPF_PROBE_MEM flag. Since the riscv JIT does not currently recognize this flag it falls back to the interpreter. Add support for BPF_PROBE_MEM, by appending an exception table to the BPF program. If the load instruction causes a data abort, the fixup infrastructure finds the exception table and fixes up the fault, by clearing the destination register and jumping over the faulting instruction. A more generic solution would add a "handler" field to the table entry, like on x86 and s390. The same issue in ARM64 is fixed in 800834285361 ("bpf, arm64: Add BPF exception tables"). Signed-off-by: Tong Tiangen <tongtiangen@huawei.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Tested-by: Pu Lehui <pulehui@huawei.com> Tested-by: Björn Töpel <bjorn@kernel.org> Acked-by: Björn Töpel <bjorn@kernel.org> Link: https://lore.kernel.org/bpf/20211027111822.3801679-1-tongtiangen@huawei.com
Diffstat (limited to 'lib/test_bpf.c')
0 files changed, 0 insertions, 0 deletions