fix(driver): avoid sending a NULL tuple in recvfrom syscall

[mrgian]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:
The kernel module and the old bpf probe send a NULL tuple to userspace when recvfrom is called with a null sockaddr pointer.
This PR fixes this behavior by getting the tuple info from the socket file descriptor itself.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

fix(driver): avoid sending a NULL tuple in `recvfrom` syscall

[github-actions]

Please double check driver/API_VERSION file. See versioning.

/hold

[leogr]

Please double check driver/API_VERSION file. See versioning.

/hold

This is a false positive for the API_VERSION. However, it seems to meet a specific case for the SCHEMA_VERSION 👇

When to increment

major version: increment when the schema becomes incompatible with previous userspace versions

minor version: increment when new features are added but existing features remain compatible (e.g. new event fields or new events)

patch version: increment when code changes don't break compatibility 👉 (e.g. bug fixes in filler code) 👈

@mrgian

So, could you bump the patch number of the schema version, please? 🙏

[mrgian]

So, could you bump the patch number of the schema version, please? 🙏

Bumped!
Forgot about that, sorry! 🤦

[FedeDP]

/milestone next-driver

[FedeDP]

Love this! Common behavior is best behavior :)
/approve

[poiana]

LGTM label has been added.

Git tree hash: a921443494431b0c7b9f851c6c23f41c18d67f49

[Andreagit97]

Thank you!
/approve

[poiana]

LGTM label has been added.

Git tree hash: b10ed3916654a6e981e068f02b588a45b8afd993

[FedeDP]

/approve

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Andreagit97, FedeDP, mrgian

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[FedeDP]

/unhold