summaryrefslogtreecommitdiff
path: root/kernel/trace/power-traces.c
diff options
context:
space:
mode:
authorPuranjay Mohan <puranjay12@gmail.com>2024-03-21 15:39:39 +0000
committerAlexei Starovoitov <ast@kernel.org>2024-03-22 20:36:36 -0700
commitf7f5d1808b1b66935a24dd796dd1a0612ca9c147 (patch)
tree620605b401cc5a3c90e78fe3620ab2a1c8d72c29 /kernel/trace/power-traces.c
parentddb2ffdc474a3000887dc776b971d04bde29decc (diff)
bpf: verifier: fix addr_space_cast from as(1) to as(0)
The verifier currently converts addr_space_cast from as(1) to as(0) that is: BPF_ALU64 | BPF_MOV | BPF_X with off=1 and imm=1 to BPF_ALU | BPF_MOV | BPF_X with imm=1 (32-bit mov) Because of this imm=1, the JITs that have bpf_jit_needs_zext() == true, interpret the converted instruction as BPF_ZEXT_REG(DST) which is a special form of mov32, used for doing explicit zero extension on dst. These JITs will just zero extend the dst reg and will not move the src to dst before the zext. Fix do_misc_fixups() to set imm=0 when converting addr_space_cast to a normal mov32. The JITs that have bpf_jit_needs_zext() == true rely on the verifier to emit zext instructions. Mark dst_reg as subreg when doing cast from as(1) to as(0) so the verifier emits a zext instruction after the mov. Fixes: 6082b6c328b5 ("bpf: Recognize addr_space_cast instruction in the verifier.") Signed-off-by: Puranjay Mohan <puranjay12@gmail.com> Link: https://lore.kernel.org/r/20240321153939.113996-1-puranjay12@gmail.com Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'kernel/trace/power-traces.c')
0 files changed, 0 insertions, 0 deletions