Bug 1232394
| Summary: | python-linux-procfs fails to read /proc/PID/flags correctly | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Hai Huang <hhuang> |
| Component: | python-linux-procfs | Assignee: | Arnaldo Carvalho de Melo <acme> |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Kastner <jkastner> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | bhu, hhuang, isenfeld, jkacur, jkastner, lmiksik, williams |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Parsing error splitting fields in python-linux-procfs
Consequence: /proc/PID/flags read incorrectly
Fix: When separating fields with spaces, take into account embedded spaces already there.
Result: /proc/PID/flags read correctly
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 12:39:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1234963 | ||
| Bug Blocks: | 1175461 | ||
|
Description
Hai Huang
2015-06-16 16:06:14 UTC
The following changes were required - procfs-Add-a-__contains__-method-to-dict-classes.patch - pidstat-Add-PF_NO_SETAFFINITY-const.patch - interrupts-Do-not-refrain-from-parsing-the-irq-affin.patch - pidstat-Fix-process_flags-method.patch - pidstat-Add-missing-PF_-flags.patch - pflags-Add-command-line-utility-to-print-processor-f.patch - pidstat-Support-COMM-names-with-spaces.patch Note, fixed in python-linux-procfs-0.4.6-3 and up Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2390.html |