Wondering where are we with this issue?
I am experiencing an issue where in a fentry/kfunc bpf probe attached to
a function doesn't fire. I have only experienced this behavior on Debian
kernels with `CONFIG_X86_KERNEL_IBT` enabled.
Because of weak symbols being removed from kallsyms,
kallsyms_lookup_size_offset() returns the symbol offset for the function
"acct_process()" more than the actual size. And the function body now
contains two __fentry__ locations.
Depending on where binary search lands up first, correct (acct_process +
4) or incorrect (acct_process + 260) location is returned.
Thanks,
Dropify
