-
Notifications
You must be signed in to change notification settings - Fork 170
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(modern): check cred
field is not NULL before the access
#2119
Conversation
Signed-off-by: Andrea Terzolo <[email protected]>
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP 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 |
LGTM label has been added. Git tree hash: 62806b3bb7d2c521b5f2e0574d8eae4cab5483a8
|
Perf diff from master - unit tests
Heap diff from master - unit tests
Heap diff from master - scap file
Benchmarks diff from master
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2119 +/- ##
=======================================
Coverage 73.69% 73.69%
=======================================
Files 253 253
Lines 31916 31915 -1
Branches 5608 5619 +11
=======================================
Hits 23521 23521
- Misses 8364 8367 +3
+ Partials 31 27 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
X64 kernel testing matrix
ARM64 kernel testing matrix
|
/milestone 0.18.2 |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area driver-modern-bpf
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
See #2118. Even if this is a possible fix to the issue I don't want to close the issue since we need to investigate more and maybe report it to COS or the upstream kernel if we notice something weird.
Since the bug doesn't depend on us I would suggest fixing it in this way (so we work again on GKE) and report it when we have enough info
Which issue(s) this PR fixes:
See #2118
Special notes for your reviewer:
Does this PR introduce a user-facing change?: