Skip to content

feat(driver)!: bump drivers' minimum required kernel version to 3.10#2722

Merged
poiana merged 1 commit intomasterfrom
ekoops/bump-to-kernel-3.10
Nov 24, 2025
Merged

feat(driver)!: bump drivers' minimum required kernel version to 3.10#2722
poiana merged 1 commit intomasterfrom
ekoops/bump-to-kernel-3.10

Conversation

@ekoops
Copy link
Copy Markdown
Contributor

@ekoops ekoops commented Nov 21, 2025

What type of PR is this?

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

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind test

/kind feature

/kind sync

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:

This PR bumps the drivers' minimum required kernel version to 3.10. In practice, this only affects the kmod driver. The kmod driver will not compile anymore on version older than 3.10, whatever is the architecture. This choice is motivated by the fact that even linux 3.10 is a 12 years old kernel, and its support ended on 2017: maintaining support for older kernel is a maintenance burden and limits progresses.

Notice that I added a build time check in the kernel module aborting the compilation on kernel < 3.10. This is redudant, as it is already checked in the driver/CMakeLists.txt, but just to be sure, in case someone tries to compile it using other mechanisms.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

/milestone next-driver

Does this PR introduce a user-facing change?:

feat(driver)!: bump drivers' minimum required kernel version to `3.10`

Signed-off-by: Leonardo Di Giovanna <leonardodigiovanna1@gmail.com>
@github-actions
Copy link
Copy Markdown

Please double check driver/SCHEMA_VERSION file. See versioning.

/hold

@codecov
Copy link
Copy Markdown

codecov bot commented Nov 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.90%. Comparing base (eca5737) to head (f71dd0b).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2722   +/-   ##
=======================================
  Coverage   76.90%   76.90%           
=======================================
  Files         296      296           
  Lines       30875    30875           
  Branches     4693     4693           
=======================================
  Hits        23745    23745           
  Misses       7130     7130           
Flag Coverage Δ
libsinsp 76.90% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@FedeDP
Copy link
Copy Markdown
Contributor

FedeDP commented Nov 22, 2025

PR LGTM! Just a side note; we should make sure to update driverkit minimum kmod version, and kernel crawler too (to avoid processing unsupported kernel versions, if any is still present in any repo).

Or we can keep them as they are now, allowing one to attempt the build of kmod against unsupported kernel releases(falling the build of course).

@ekoops
Copy link
Copy Markdown
Contributor Author

ekoops commented Nov 22, 2025

PR LGTM! Just a side note; we should make sure to update driverkit minimum kmod version, and kernel crawler too (to avoid processing unsupported kernel versions, if any is still present in any repo).

Or we can keep them as they are now, allowing one to attempt the build of kmod against unsupported kernel releases(falling the build of course).

Agree! I'll take care of updating the minimum version for driverkit and the kernel crawler

@ekoops
Copy link
Copy Markdown
Contributor Author

ekoops commented Nov 24, 2025

Please double check driver/SCHEMA_VERSION file. See versioning.

/hold

False positive. No need to update SCHEMA_VERSION.

@ekoops
Copy link
Copy Markdown
Contributor Author

ekoops commented Nov 24, 2025

/remove-hold

Copy link
Copy Markdown
Contributor

@irozzo-1A irozzo-1A left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Do you have a PR to update the docs already?

Copy link
Copy Markdown
Member

@deepskyblue86 deepskyblue86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice cleanup (finally)!
/approve

@github-project-automation github-project-automation bot moved this from Todo to In progress in Falco Roadmap Nov 24, 2025
@poiana
Copy link
Copy Markdown
Contributor

poiana commented Nov 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepskyblue86, ekoops, irozzo-1A

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

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [deepskyblue86,ekoops]

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

@poiana poiana merged commit e231639 into master Nov 24, 2025
65 of 93 checks passed
@github-project-automation github-project-automation bot moved this from In progress to Done in Falco Roadmap Nov 24, 2025
@poiana poiana deleted the ekoops/bump-to-kernel-3.10 branch November 24, 2025 09:00
@FedeDP
Copy link
Copy Markdown
Contributor

FedeDP commented Nov 24, 2025

@ekoops perhaps it would be even better to avoid touching kernel-crawler (whose output should be as agnostic as possible) and let dbg-go avoid generating driverkit configs for unsupported kernel releases (by driverkit ofc), somewhere around here i'd say: https://github.com/falcosecurity/dbg-go/blob/main/pkg/generate/generate.go#L131 (perhaps put this behavior behind a CLI flag?)

@ekoops
Copy link
Copy Markdown
Contributor Author

ekoops commented Nov 24, 2025

I forgot to mention that this bump is a pre-requisite for an upcoming fix related to #2709 .

@ekoops
Copy link
Copy Markdown
Contributor Author

ekoops commented Nov 24, 2025

@ekoops perhaps it would be even better to avoid touching kernel-crawler (whose output should be as agnostic as possible) and let dbg-go avoid generating driverkit configs for unsupported kernel releases (by driverkit ofc), somewhere around here i'd say: https://github.com/falcosecurity/dbg-go/blob/main/pkg/generate/generate.go#L131 (perhaps put this behavior behind a CLI flag?)

I'll take a look at dbg-go. I didn't know about it. Thank you 😄

@ekoops
Copy link
Copy Markdown
Contributor Author

ekoops commented Nov 26, 2025

/lgtm

Do you have a PR to update the docs already?

Sorry I didn't see your message. Not yet, I have in my TODO list, besides looking at dbg-go to stop generating configurations for unsupported kernel releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

5 participants