-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(driver): fixed build against 6.6 rc kernel. #1349
Conversation
/milestone 6.0.1+driver |
Please double check driver/API_VERSION file. See versioning. /hold |
/unhold |
driver/API_VERSION
Outdated
@@ -1 +1 @@ | |||
5.0.0 | |||
5.0.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Milestone is 6.0.1+driver but this reads 5.0.1 . Why is that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because we were already at 6.0.0+driver (latest tagged), since we bump major when either SCHEMA or API have major bumps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that's the API version, sure! Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure we need an API bump here. This version regulates the API between userspace and drivers but here we don't change it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need it: we are releasing a new driver tag and it needs a minor bump in order to have different tag name (i think).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I double checked; it does not seem like we need to bump in this case.
/cc @Andreagit97 |
/hold |
/unhold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like it might be worth it to create a helper function inside kernel_hacks.h
(which is what that file is there for, after all).
We are not using that file since ages though :) But that's just my 2c and my taste. I know it gets much more "spaghetti" than it would need, but that's just what kernel allows us to do. |
driver/API_VERSION
Outdated
@@ -1 +1 @@ | |||
5.0.0 | |||
5.0.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure we need an API bump here. This version regulates the API between userspace and drivers but here we don't change it
driver/modern_bpf/programs/attached/events/sched_process_exec.bpf.c
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fact that we are breaking our drivers at every kernel release IMO is a clear signal that we are hooking in place in which we shouldn't hook. Maybe we should take some time to reflect on this :/
cf47bd6
to
c788184
Compare
Signed-off-by: Federico Di Pierro <[email protected]>
Signed-off-by: Federico Di Pierro <[email protected]>
Signed-off-by: Federico Di Pierro <[email protected]> Co-authored-by: Andrea Terzolo <[email protected]>
c788184
to
52da8ed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
Thank you!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP, leogr 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:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area driver-kmod
/area driver-bpf
/area driver-modern-bpf
What this PR does / why we need it:
See torvalds/linux@13bc244
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: