fix(driver/bpf): fix socket_x and socketpair_x domain encoding#2477
fix(driver/bpf): fix socket_x and socketpair_x domain encoding#2477
socket_x and socketpair_x domain encoding#2477Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ekoops The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/milestone 0.22.0 |
|
Please double check driver/SCHEMA_VERSION file. See versioning. /hold |
Perf diff from master - unit testsHeap diff from master - unit testsHeap diff from master - scap fileBenchmarks diff from master |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2477 +/- ##
=======================================
Coverage 77.88% 77.88%
=======================================
Files 251 251
Lines 31071 31071
Branches 4653 4653
=======================================
Hits 24201 24201
Misses 6870 6870
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3e2c78d to
d7e4911
Compare
X64 kernel testing matrix
ARM64 kernel testing matrix
|
|
Unfortunately, splitting the fillers into two smaller ones didn't fix the issue. I'll use this PR to experiment and trying to find a solution. |
51a0c6b to
cd5ad61
Compare
cd5ad61 to
c7ebd80
Compare
c7ebd80 to
bf65765
Compare
bd3e81c to
823d001
Compare
823d001 to
4d7e410
Compare
4d7e410 to
30a9a08
Compare
30a9a08 to
962dfbf
Compare
f_sys_socketpair_x into two fillerssocket_x and socketpair_x domain encoding
Partially revert changes introduced in dfdd45c by replacing the usage of `socket_family_to_scap` helper with a calls to a new ad-hoc helper for the legacy bpf probe. To avoid breaking the verifier on old kernel version, just convert user-provided negative socket family values to `PPM_AF_UNSPEC` and leave positive values as are. This simplified version relies on the fact that `AF_*` and corresponding `PPM_AF_*` macros map to the same values. Signed-off-by: Leonardo Di Giovanna <leonardodigiovanna1@gmail.com>
962dfbf to
95b08f0
Compare
|
New changes pushed, and fortunately, everything works now 😄. The schema version error is a false positive. |
|
LGTM label has been added. DetailsGit tree hash: b44bd97a9fd37b9b52908b4c5a0a5e47b575b7e1 |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area driver-bpf
Does this PR require a change in the driver versions?
What this PR does / why we need it:
This PR partially reverts changes introduced in commit dfdd45c (#2470) by replacing the usage of
socket_family_to_scaphelper with a calls to a new ad-hoc helper for the legacy bpf probe. To avoid breaking the verifier on old kernel version (i.e.oraclelinux-4.14), just convert user-provided negative socket family values toPPM_AF_UNSPECand leave positive values as are. This simplified version relies on the fact thatAF_*and correspondingPPM_AF_*macros map to the same values.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: