Bug 627901
| Summary: | Segfault when decoding DMI data in dmi_processor_id() | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Roman Rakus <rrakus> |
| Component: | python-dmidecode | Assignee: | Roman Rakus <rrakus> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.1 | CC: | azelinka, davids, jhutar, jplans, jscotka, jwest, mcermak, mwhitehe, ovasik, psklenar, rrakus, rvokal, tao, tsmetana, williams |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-dmidecode-3.10.13-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, certain DMI (Direct Media Interface) tables did not report CPU information as a string and returned the NULL value instead. Consequently, Python terminated unexpectedly with a segmentation fault when trying to identify the CPU type by performing a string comparison. With this update, additional checks for NULL values, performed prior the string comparison, have been added to the code, thus fixing this bug.
|
Story Points: | --- |
| Clone Of: | 596264 | Environment: | |
| Last Closed: | 2011-12-06 11:51:40 UTC | Type: | --- |
| 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: | |||
| Bug Blocks: | 726613, 726614 | ||
|
Comment 3
Roman Rakus
2011-06-29 16:33:56 UTC
Proposed for z-streams based on request from Matthew Whitehead
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When trying to identify the processor type by performing a string comparison, Python terminated with a segmentation fault. This was caused by DMI tables which did not report the CPU processor information as a string and returned a NULL value instead. This update adds additional checks for NULL values before doing the string comparison.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-When trying to identify the processor type by performing a string comparison, Python terminated with a segmentation fault. This was caused by DMI tables which did not report the CPU processor information as a string and returned a NULL value instead. This update adds additional checks for NULL values before doing the string comparison.+Previously, certain DMI (Direct Media Interface) tables did not report CPU information as a string and returned the NULL value instead. Consequently, Python terminated unexpectedly with a segmentation fault when trying to identify the CPU type by performing a string comparison. With this update, additional checks for NULL values, performed prior the string comparison, have been added to the code, thus fixing this bug.
(In reply to comment #9) > Technical note updated. If any revisions are required, please edit the > "Technical Notes" field > accordingly. All revisions will be proofread by the Engineering Content > Services team. > > Diffed Contents: > @@ -1 +1 @@ > -When trying to identify the processor type by performing a string comparison, > Python terminated with a segmentation fault. This was caused by DMI tables > which did not report the CPU processor information as a string and returned a > NULL value instead. This update adds additional checks for NULL values before > doing the string comparison.+Previously, certain DMI (Direct Media Interface) > tables did not report CPU information as a string and returned the NULL value > instead. Consequently, Python terminated unexpectedly with a segmentation fault > when trying to identify the CPU type by performing a string comparison. With > this update, additional checks for NULL values, performed prior the string > comparison, have been added to the code, thus fixing this bug. Just a heads up, the DMI abbreviation is wrong. From the man page of dmidecode: dmidecode is a tool for dumping a computer's DMI (some say SMBIOS) table contents in a human-readable format. [...snip...] SMBIOS stands for System Management BIOS, while DMI stands for Desktop Management Interface. Both standards are tightly related and developed by the DMTF (Desktop Management Task Force). 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. http://rhn.redhat.com/errata/RHBA-2011-1589.html |