libbpf: reject legacy 'maps' ELF section
Andrii Nakryiko
maintainerPATCH 1/1 libbpf: reject legacy 'maps' ELF section
Add explicit error message if BPF object file is still using legacy BPF map definitions in SEC("maps"). Before this change, if BPF object file is still using legacy map definition user will see a bit confusing:
libbpf: elf: skipping unrecognized data section(4) maps
libbpf: prog 'handler': bad map relo against 'server_map' in section 'maps'
Now libbpf will be explicit about rejecting "maps" ELF section:
libbpf: elf: legacy map definitions in 'maps' section are not supported by libbpf v1.0+
--- tools/lib/bpf/libbpf.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)
tools/lib/bpf/libbpf.c +3 -5
@@ -591,7 +591,6 @@ struct elf_state {size_t strtabidx;struct elf_sec_desc *secs;int sec_cnt; -int maps_shndx;int btf_maps_shndx;__u32 btf_maps_sec_btf_id;int text_shndx;
@@ -1272,7 +1271,6 @@ static struct bpf_object *bpf_object__new(const char *path,*/ obj->efile.obj_buf = obj_buf; obj->efile.obj_buf_sz = obj_buf_sz; - obj->efile.maps_shndx =-1 ; obj->efile.btf_maps_shndx =-1 ; obj->efile.st_ops_shndx =-1 ; obj->kconfig_map_idx =-1 ;
@@ -3359,7 +3357,8 @@ static int bpf_object__elf_collect(struct bpf_object *obj)if (err)return err; }else if (strcmp (name,"maps" ) ==0 ) { - obj->efile.maps_shndx = idx; +pr_warn ("elf: legacy map definitions in 'maps' section are not supported by libbpf v1.0+\n" ); +return -ENOTSUP ; }else if (strcmp (name,MAPS_ELF_SEC ) ==0 ) { obj->efile.btf_maps_shndx = idx; }else if (strcmp (name,BTF_ELF_SEC ) ==0 ) {
@@ -3891,8 +3890,7 @@ static bool bpf_object__shndx_is_data(const struct bpf_object *obj,static bool bpf_object__shndx_is_maps (const struct bpf_object *obj,int shndx) { -return shndx == obj->efile.maps_shndx || - shndx == obj->efile.btf_maps_shndx; +return shndx == obj->efile.btf_maps_shndx; } static enum libbpf_map_type
Signature · 1 line
2.30.2
This patch was applied to bpf/bpf-next.git (master) by Daniel Borkmann <[email protected]>:
Hello:
This patch was applied to bpf/bpf-next.git (master) by Daniel Borkmann <[email protected]>:
Quoted 8 lines · On Wed, 3 Aug 2022 14:42:02 -0700 you wrote:
Add explicit error message if BPF object file is still using legacy BPF map definitions in
SEC("maps"). Before this change, if BPF object file is still using legacy map definition user will see a bit confusing:libbpf: elf: skipping unrecognized data section(4) maps
libbpf: prog 'handler': bad map relo against 'server_map' in section 'maps'[...]
Here is the summary with links:
- [bpf-next] libbpf: reject legacy 'maps' ELF section
https://git.kernel.org/bpf/bpf-next/c/e19db6762c18
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html