-
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(userspace/libsinsp): use comm
file instead of status
to get proc comm
#2197
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
/milestone 0.20.0 |
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 #2197 +/- ##
==========================================
- Coverage 75.19% 75.19% -0.01%
==========================================
Files 259 259
Lines 33875 33878 +3
Branches 5800 5801 +1
==========================================
+ Hits 25473 25475 +2
- Misses 8402 8403 +1
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
|
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.
Good catch! 👍
SGTM, just some nits:
- See my comment below
- I guess we need to update the documentation of the
proc.name
and switch from/proc/PID/status
to/proc/PID/comm
"from the syscalls args or, as a fallback, extracted from /proc/PID/status. The name of "
…roc comm. Signed-off-by: Federico Di Pierro <[email protected]> Co-authored-by: <[email protected]>
dac36cd
to
1120ca4
Compare
@leogr fixed the filtercheck description, thanks for the catch! |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area libscap
What this PR does / why we need it:
When scanning proc from scap, make sure to use
comm
file to parse threadinfo comm field, instead of usingstatus
file and grepping forName:%1024s
. Also, usingsscanf
in that way does not support strings with spaces, ie: if a status file was likewe would only load
foo
.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: