Signatures of functions for attach_uretprobe #4942
Unanswered
christian-2
asked this question in
Q&A
Replies: 1 comment
-
Or can/should one perhaps look up all. arguments with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the right signature for a function that is attached through
attach_uretprobe()
?From function
probe_SSL_read_exit()
intools/sslsniff.py
is appears that it comprises only a single argument of typestruct pt_regs *
.From function
probe_SSL_read_exit()
in/user/sbin/sslsniff-bpfcc
(the version that comes with Debian packagebpfcc-tools=0.18.0+ds-2
) it appears that it is the same as forprobe_SSL_read_enter()
, i.e. that it comprises an argument of typestruct pt_regs *
plus other arguments corresponding to the signature ofSSL_read()
. But there is also a comment that says "It looks like SSL_read's arguments aren't available in a return probe" and logic to account for that.So is it correct to assume that the signature in
tools/sslsniff.py
is the correct one and that the other one (in/user/sbin/sslsniff-bpfcc
) is incorrect or outdated?Beta Was this translation helpful? Give feedback.
All reactions