Bug 1691705

Summary:	Let squash module save more space by allowing dropping swith-root ability
Product:	Red Hat Enterprise Linux 8	Reporter:	Kairui Song <kasong>
Component:	dracut	Assignee:	Lukáš Nykrýn <lnykryn>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	dracut-maint-list, jstodola, kasong, pkotvan, xiawu
Target Milestone:	rc	Keywords:	OtherQA
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dracut-049-24.git20190802.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:27:05 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:
Bug Depends On:
Bug Blocks:	1692632

Description Kairui Song 2019-03-22 09:57:38 UTC

Description of problem:
There are some upstream work on squash module to allow it save more space, and save memory by dropping swith-root ability. Backporting it will improve kdump memory usage and solve more OOM issues.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Currently pending PR:
https://github.com/dracutdevs/dracut/pull/552

Comment 1 Peter Kotvan 2019-08-02 05:37:10 UTC

It was agreed that Xiaowu Wu will test kdump against the final build of dracut. qa_ack+ granted.

Comment 4 Jan Stodola 2019-08-30 14:35:32 UTC

Thank you for testing, Emma.
I'm moving this bug to VERIFIED based on comment 3.

Comment 7 errata-xmlrpc 2019-11-05 22:27:05 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-2019:3604