Bug 1766358

Summary: VDO can still issue I/O when suspended
Product: Red Hat Enterprise Linux 8 Reporter: corwin <corwin>
Component: kmod-kvdoAssignee: corwin <corwin>
Status: CLOSED ERRATA QA Contact: Filip Suba <fsuba>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: awalsh, fsuba
Target Milestone: rc   
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 6.2.2.114 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:43:10 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:

Description corwin 2019-10-28 20:14:34 UTC
Description of problem:
In some rare circumstances, there is a race which could result in a VDO issuing I/O to the underlying storage after the VDO has been suspended.

Version-Release number of selected component (if applicable):
6.2.1.138

How reproducible:
Very rare. We have never directly observed this bug in the kernel. We have seen it quite rarely in our internal user-space unit testing.

Comment 4 Filip Suba 2020-03-16 14:13:06 UTC
Verified SanityOnly with vdo-6.2.2.117-13.el8.

Comment 6 errata-xmlrpc 2020-04-28 16:43:10 UTC
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-2020:1782