RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1658348 - vdo postsuspend allocates memory, doesn't handle IO error
Summary: vdo postsuspend allocates memory, doesn't handle IO error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Sweet Tea Dorminy
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-11 20:17 UTC by Sweet Tea Dorminy
Modified: 2021-09-06 15:23 UTC (History)
3 users (show)

Fixed In Version: 6.2.0.290
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 01:52:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-19873 0 None None None 2021-09-06 15:23:04 UTC

Description Sweet Tea Dorminy 2018-12-11 20:17:37 UTC 
Description of problem:
VDO's post-suspend function does a flush to the storage under it. It allocates memory to do this flush, and does not enter read-only mode if it gets an error on this flush. It shouldn't allocate, and should enter read-only. 

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

How reproducible:
Not particulrly.

Steps to Reproduce:
1. Make VDO suspend in a memory-constrained environment, or where it gets an io error on its final flush.

Actual results:
Observe hanging for mem allocation, or failure to enter read only mode.


Expected results:
No memory allocation, and read-only mode upon error.
Comment 2 Jakub Krysl 2019-02-14 09:04:53 UTC 
Regression testing passed with following versions:

kernel-4.18.0-64.el8.x86_64
kmod-kvdo-6.2.0.293-44.el8.x86_64
vdo-6.2.0.293-10.el8.x86_64
Note You need to log in before you can comment on or make changes to this bug.