cgrulesengd cannot process symlinked executables
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libcgroup (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Serge Hallyn |
Bug Description
Oh hai!
I've found that 0.37.1-1ubuntu10 in precise/LTS cannot process symlinked executables correctly, the testcase is
>$ python -c "import time; time.sleep(2)" & cgclassify $!
>Error in determining process name of pid 9738
The issue was fixed upstream in v0.38, see https:/
It will be awesome if the patch will be applied to v0.37 in precise/LTS, because right now cgrulesengd/
=======
SRU Justification:
1. Impact: symlinked executables cannot be classified
2. Development fix: in the case of a symlink, read the real
file path from /proc/self/exe
3. Stable fix: cherrypick small patch from development fix.
4. Test case: see comment #5.
5. Regression potential: there should be none, as this fix is
taken straight from upstream and only affects the path when
a symbolic link is being run (which is already broken).
=======
Related branches
description: | updated |
Changed in libcgroup (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in libcgroup (Ubuntu Precise): | |
status: | New → In Progress |
assignee: | nobody → Serge Hallyn (serge-hallyn) |
importance: | Undecided → High |
Thanks for reporting this bug and pointing to the nice simple fix. I"ll work on SRUing this.
Would you mind adding a detailed test case to the description? (The symlinking part is fine, but the configuration file plus a neat way to determine that the task failed to be reclassified.)