diff options
author | Andrii Nakryiko <andrii@kernel.org> | 2023-12-14 17:13:28 -0800 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2023-12-19 18:06:46 -0800 |
commit | c5a7244759b1eeacc59d0426fb73859afa942d0d (patch) | |
tree | bdc7b9d4e0dc6d2d81f457fdb87a9209b7597d75 /crypto/cfb.c | |
parent | e26080d0da87f20222ca6712b65f95a856fadee0 (diff) | |
download | linux-stable-c5a7244759b1eeacc59d0426fb73859afa942d0d.tar.gz linux-stable-c5a7244759b1eeacc59d0426fb73859afa942d0d.tar.bz2 linux-stable-c5a7244759b1eeacc59d0426fb73859afa942d0d.zip |
bpf: move subprog call logic back to verifier.c
Subprog call logic in btf_check_subprog_call() currently has both a lot
of BTF parsing logic (which is, presumably, what justified putting it
into btf.c), but also a bunch of register state checks, some of each
utilize deep verifier logic helpers, necessarily exported from
verifier.c: check_ptr_off_reg(), check_func_arg_reg_off(),
and check_mem_reg().
Going forward, btf_check_subprog_call() will have a minimum of
BTF-related logic, but will get more internal verifier logic related to
register state manipulation. So move it into verifier.c to minimize
amount of verifier-specific logic exposed to btf.c.
We do this move before refactoring btf_check_func_arg_match() to
preserve as much history post-refactoring as possible.
No functional changes.
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/r/20231215011334.2307144-5-andrii@kernel.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'crypto/cfb.c')
0 files changed, 0 insertions, 0 deletions