Re: Reading Pinned maps in eBPF Programs


Ian
 

Hello, 

Here is the libbpf Logs at all levels for the open snoop program when using the pinned option for a map. This was tested on Linux Kernel v5.4 with libbpf 0.0.9, 0.1.0, and the current version. All the results of the logs were the same so I have only posted a single copy of it here. Let me know what you think and what the next steps might be! I appreciate the help and am having a good time trying to piece this together. 

libbpf: loading bpf-library/bpf_objs/opensnoop.bpf.o
 
libbpf: section(1) .strtab, size 289, link 0, flags 0, type=3
 
libbpf: skip section(1) .strtab
 
libbpf: section(2) .text, size 0, link 0, flags 6, type=1
 
libbpf: skip section(2) .text
 
libbpf: section(3) tracepoint/syscalls/sys_enter_openat, size 1632, link 0, flags 6, type=1
 
libbpf: found program tracepoint/syscalls/sys_enter_openat
 
libbpf: section(4) .reltracepoint/syscalls/sys_enter_openat, size 32, link 15, flags 0, type=9
 
libbpf: section(5) tracepoint/syscalls/sys_enter_open, size 1368, link 0, flags 6, type=1
 
libbpf: found program tracepoint/syscalls/sys_enter_open
 
libbpf: section(6) .reltracepoint/syscalls/sys_enter_open, size 32, link 15, flags 0, type=9
 
libbpf: section(7) .data, size 4, link 0, flags 3, type=1
 
libbpf: section(8) maps, size 20, link 0, flags 3, type=1
 
libbpf: section(9) .rodata.str1.1, size 9, link 0, flags 32, type=1
 
libbpf: skip section(9) .rodata.str1.1
 
libbpf: section(10) version, size 4, link 0, flags 3, type=1
 
libbpf: kernel version of bpf-library/bpf_objs/opensnoop.bpf.o is 50422
 
libbpf: section(11) license, size 4, link 0, flags 3, type=1
 
libbpf: license of bpf-library/bpf_objs/opensnoop.bpf.o is GPL
 
libbpf: section(12) .maps, size 40, link 0, flags 3, type=1
 
libbpf: section(13) .eh_frame, size 80, link 0, flags 2, type=1
 
libbpf: skip section(13) .eh_frame
 
libbpf: section(14) .rel.eh_frame, size 32, link 15, flags 0, type=9
 
libbpf: skip relo .rel.eh_frame(14) for section(13)
 
libbpf: section(15) .symtab, size 408, link 1, flags 0, type=2
 
libbpf: BTF is required, but is missing or corrupted.
 
Ian

Join iovisor-dev@lists.iovisor.org to automatically receive all group messages.