[tcp_stats] Use kfuncs to probe the tcp_sendmsg function #2072
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary: Adds kfunc support to BCC wrapper and utilizes it to probe the
tcp_sendmsg
function from the tcp stats connector.We had seen a kprobe attachment conflict when the socket tracer and tcp stats connectors were enabled in Stirling due to both connectors trying to deploy kprobes for
tcp_sendmsg
. This PR modifies the tcp stats connector to instead deploy a kfunc probe to avoid the conflict.Relevant Issues: #2055
Type of change: /kind bug
Test Plan: Skaffolded these changes on a dev cluster with socket tracer and tcp stats enabled and verified the existing tcp stats BPF test passes on kernel version
6.8.0-1018-gcp
Relevant parts of the pem logs from skaffolding: