chore(aya): Use BPF_ADD from bindings

We should use the generated one, not the one provided by the libc crate.

Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
pull/1240/head
Dave Tucker 2 weeks ago
parent 756d8172f5
commit 23a5e06c75

@ -15,14 +15,14 @@ use aya_obj::{
VarLinkage,
},
generated::{
BPF_ALU64, BPF_CALL, BPF_DW, BPF_EXIT, BPF_F_REPLACE, BPF_IMM, BPF_JMP, BPF_K, BPF_LD,
BPF_MEM, BPF_MOV, BPF_PSEUDO_MAP_VALUE, BPF_ST, BPF_X, bpf_attach_type, bpf_attr,
BPF_ADD, BPF_ALU64, BPF_CALL, BPF_DW, BPF_EXIT, BPF_F_REPLACE, BPF_IMM, BPF_JMP, BPF_K,
BPF_LD, BPF_MEM, BPF_MOV, BPF_PSEUDO_MAP_VALUE, BPF_ST, BPF_X, bpf_attach_type, bpf_attr,
bpf_btf_info, bpf_cmd, bpf_func_id::*, bpf_insn, bpf_link_info, bpf_map_info, bpf_map_type,
bpf_prog_info, bpf_prog_type, bpf_stats_type,
},
maps::{LegacyMap, bpf_map_def},
};
use libc::{BPF_ADD, ENOENT, ENOSPC};
use libc::{ENOENT, ENOSPC};
use crate::{
Btf, FEATURES, Pod, VerifierLogLevel,

Loading…
Cancel
Save