Back to bug 1385410
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Evan McNabb | 2016-10-17 14:51:00 UTC | QA Contact | kernel-qe-hw | mgahagan |
| Dan Kenigsberg | 2016-10-19 07:07:14 UTC | Target Release | --- | 7.4 |
| CC | danken | |||
| Siddharth Nagar | 2016-11-09 15:02:37 UTC | Priority | unspecified | high |
| Linqing Lu | 2016-11-14 06:34:36 UTC | Blocks | 1394638 | |
| Linqing Lu | 2016-12-13 15:14:01 UTC | Blocks | 1404314 | |
| Petr Oros | 2017-03-13 15:41:22 UTC | Status | NEW | MODIFIED |
| Fixed In Version | python-dmidecode-3.12.2-1.el7 | |||
| errata-xmlrpc | 2017-03-13 15:45:04 UTC | Status | MODIFIED | ON_QA |
| Jaroslav Reznik | 2017-03-13 16:02:38 UTC | Blocks | 1431702 | |
| Jaroslav Reznik | 2017-03-13 16:03:06 UTC | Keywords | ZStream | |
| Mike Gahagan | 2017-04-19 19:04:21 UTC | Status | ON_QA | VERIFIED |
| Lenka Špačková | 2017-06-20 14:10:21 UTC | Doc Text | Previously, the dmidecode Python module did not check for presence of entries in the Desktop Management Interface (DMI) table and was unable to handle malformed data when querying the DMI table. As a consequence, when querying a non-existent or invalid DMI table entry, the dmidecode module terminated unexpectedly with a segmentation fault. This update adds a check for the presence and format of the DMI table entries. As a result, the dmidecode module no longer terminates with a segmentation fault when querying malformed DMI tables, and correctly returns empty data in the described situation. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2017-08-01 19:18:00 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-01 15:18:00 UTC | |||
| Brendan Conoboy | 2019-02-15 03:10:24 UTC | Pool ID | 70 | 136 |
Back to bug 1385410