summaryrefslogtreecommitdiffstats
path: root/certs
diff options
context:
space:
mode:
authorSandipan Das <sandipan@linux.vnet.ibm.com>2018-05-24 12:26:50 +0530
committerDaniel Borkmann <daniel@iogearbox.net>2018-05-24 09:20:49 +0200
commitf84192ee00b7d8b3c38545d3a61d4191f80cc81a (patch)
tree236e1f0dada1768797eafacdb707fcce1b59ceb9 /certs
parentdd0c5f072e650458feb307fe3a8602cc2ec369d4 (diff)
downloadop-kernel-dev-f84192ee00b7d8b3c38545d3a61d4191f80cc81a.zip
op-kernel-dev-f84192ee00b7d8b3c38545d3a61d4191f80cc81a.tar.gz
tools: bpftool: resolve calls without using imm field
Currently, we resolve the callee's address for a JITed function call by using the imm field of the call instruction as an offset from __bpf_call_base. If bpf_jit_kallsyms is enabled, we further use this address to get the callee's kernel symbol's name. For some architectures, such as powerpc64, the imm field is not large enough to hold this offset. So, instead of assigning this offset to the imm field, the verifier now assigns the subprog id. Also, a list of kernel symbol addresses for all the JITed functions is provided in the program info. We now use the imm field as an index for this list to lookup a callee's symbol's address and resolve its name. Suggested-by: Daniel Borkmann <daniel@iogearbox.net> Signed-off-by: Sandipan Das <sandipan@linux.vnet.ibm.com> Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud