Bug 1567744
| Summary: | Hang or NULL pointer dereference if reading sysfs during VDO start/stop. [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | kmod-kvdo | Assignee: | Thomas Jaskiewicz <tjaskiew> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.5 | CC: | awalsh, bgurney, jkrysl, rhandlin, sweettea, tjaskiew |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.0.164 | Doc Type: | If docs needed, set a value |
| Doc Text: |
When a process was reading Virtual Data Optimizer (VDO) sysfs entries while a VDO volume was starting up or shutting down, the process and the VDO task sometimes became unresponsive or terminated unexpectedly. With this update, the sysfs entries are created and released at the correct time. As a result, the described problem no longer occurs
|
Story Points: | --- |
| Clone Of: | 1559692 | Environment: | |
| Last Closed: | 2018-05-14 16:13:32 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: | 1559692 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-04-16 07:03:27 UTC
Using the reproducer I was not able to get vdo to hang or get any calltrace. Reading from /sys correctly produces either value ('0') or error ('cat: /sys/kvdo/vdo0/statistics/data_blocks_used: No such file or directory'). The start/stop cycle keeps going.
No regressions found as regression testing passed.
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://access.redhat.com/errata/RHBA-2018:1407 |