Bug 1619605
| Summary: | NULL pointer dereference while deleting VDO volumes that had been used for stacked raid testing [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | kmod-kvdo | Assignee: | Matthew Sakai <msakai> |
| Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> |
| Severity: | medium | Docs Contact: | Marie Hornickova <mdolezel> |
| Priority: | high | ||
| Version: | 7.6 | CC: | awalsh, cmarthal, jkrysl, limershe, msakai, rhandlin |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.0.185 | Doc Type: | Bug Fix |
| Doc Text: |
When the write policy of a VDO device was set to "sync", or if the underlying storage device did not accept flushes, the VDO recovery journal thread overflowed its available stack space during a reaping operation. Consequently, the stack frames were corrupted, and some errors such as NULL pointer dereferences occurred. With this update, the recovery journal reaping code has been restructured to strictly limit thread stack size. As a result, the stack can no longer overflow, and the thread state corruption no longer occurs under the described circumstances.
|
Story Points: | --- |
| Clone Of: | 1608070 | Environment: | |
| Last Closed: | 2018-11-06 16:16:04 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: | 1608070 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-08-21 09:59:12 UTC
We're no longer seeing this issue after stacked raid10/raid* vdo tests are run and cleaned up for additional testing. Marking verified in the latest rpms. [lvm_vdo_raid] [lvm_vdo_raid_sanity_raid10] PASS [lvm_vdo_raid] [lvm_vdo_raid_sanity_raid1] PASS [lvm_vdo_raid] [lvm_vdo_raid_sanity_raid4] PASS [lvm_vdo_raid] [lvm_vdo_raid_sanity_raid5] PASS 3.10.0-862.20.1.el7.x86_64 BUILT: Mon 01 Oct 2018 06:04:56 AM CDT vdo-6.1.0.185-18 BUILT: Thu Sep 6 13:56:35 CDT 2018 kmod-kvdo-6.1.0.185-17.el7_5 BUILT: Thu Sep 6 13:58:04 CDT 2018 lvm2-2.02.177-4.el7_5.1 BUILT: Tue Sep 18 08:47:25 CDT 2018 lvm2-libs-2.02.177-4.el7_5.1 BUILT: Tue Sep 18 08:47:25 CDT 2018 device-mapper-1.02.146-4.el7_5.1 BUILT: Tue Sep 18 08:47:25 CDT 2018 device-mapper-libs-1.02.146-4.el7_5.1 BUILT: Tue Sep 18 08:47:25 CDT 2018 device-mapper-event-1.02.146-4.el7_5.1 BUILT: Tue Sep 18 08:47:25 CDT 2018 device-mapper-event-libs-1.02.146-4.el7_5.1 BUILT: Tue Sep 18 08:47:25 CDT 2018 vdo-6.1.0.185-18 BUILT: Thu Sep 6 13:56:35 CDT 2018 kmod-kvdo-6.1.0.185-17.el7_5 BUILT: Thu Sep 6 13:58:04 CDT 2018 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:3509 |