Bug 1824789

Summary:	Potential IO in progress while suspended/removed.
Product:	Red Hat Enterprise Linux 8	Reporter:	Sweet Tea Dorminy <sweettea>
Component:	kmod-kvdo	Assignee:	Sweet Tea Dorminy <sweettea>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	awalsh, corwin, fsuba
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.6.3.91	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 02:01:47 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 Sweet Tea Dorminy 2020-04-16 12:58:25 UTC

Description of problem:
At the present time, RJ reaping does not stop when we suspend the recovery journal. This means that slab suspend may release recovery journal locks, resulting the journal potentially reaping and thereby doing some flushes.

This has two implications: 
1) IO during suspend may be paused indefinitely, so it should be avoided.
2) Reaping could begin during suspend, and repeat so that the final flush issued by reaping returns after the VDO has been freed. This use-after-free may cause crashes.


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

How reproducible:
Very hard. Only observed in a unit test, once.

Steps to Reproduce:
1. Unknown. Sanity-only?

Comment 3 Filip Suba 2020-08-21 07:41:29 UTC

Verified SanityOnly. Regression testing passed.

Comment 6 errata-xmlrpc 2020-11-04 02:01:47 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 (kmod-kvdo bug fix and enhancement update), 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:4551