bpf: Enforce returning 0 for fentry/fexit progs
authorYonghong Song <yhs@fb.com>
Thu, 14 May 2020 05:32:05 +0000 (22:32 -0700)
committerAlexei Starovoitov <ast@kernel.org>
Thu, 14 May 2020 19:50:10 +0000 (12:50 -0700)
commite92888c72fbdc6f9d07b3b0604c012e81d7c0da7
treeb2ad05c336d5bb8cf8cbbc5081f8848338516263
parent625236ba3832ae947cb3ebb7acc1f30788b274ef
bpf: Enforce returning 0 for fentry/fexit progs

Currently, tracing/fentry and tracing/fexit prog
return values are not enforced. In trampoline codes,
the fentry/fexit prog return values are ignored.
Let us enforce it to be 0 to avoid confusion and
allows potential future extension.

This patch also explicitly added return value
checking for tracing/raw_tp, tracing/fmod_ret,
and freplace programs such that these program
return values can be anything. The purpose are
two folds:
 1. to make it explicit about return value expectations
    for these programs in verifier.
 2. for tracing prog_type, if a future attach type
    is added, the default is -ENOTSUPP which will
    enforce to specify return value ranges explicitly.

Fixes: fec56f5890d9 ("bpf: Introduce BPF trampoline")
Signed-off-by: Yonghong Song <yhs@fb.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Andrii Nakryiko <andriin@fb.com>
Link: https://lore.kernel.org/bpf/20200514053206.1298415-1-yhs@fb.com
kernel/bpf/verifier.c