Bug 1559460

Summary: Rebase request for crash utility RHEL7.6 errata
Product: Red Hat Enterprise Linux 7 Reporter: Dave Anderson <anderson>
Component: crashAssignee: Dave Anderson <anderson>
Status: CLOSED ERRATA QA Contact: Emma Wu <xiawu>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.6CC: qzhao, salmy
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: crash-7.2.3-2.el7 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Important: if this rebase instead contains *only bug fixes,* or *only enhancements*, select the correct option from the Doc Type drop-down list. Rebase package(s) to version: crash-7.2.1 Highlights, important fixes, or notable enhancements: Full changelog: http://people.redhat.com/anderson/crash.changelog.html#7_2_1
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:30:21 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 Dave Anderson 2018-03-22 15:35:00 UTC
Description of problem:

The RHEL7.6 errata version of the crash utility should be
rebased to the current upstream version, currently at version
crash-7.2.1.  There are several new features and other bug fixes
that have been applied to the upstream version make the tool 
significantly more useful than the current RHEL7.5 version.
This includes fixes, optimizations and updates for the "kmem", 
"bt" and "ps" commands, initial support for 5-level page tables
and other Linux 4.16 requirements.

Furthermore, since crash-7.2.1 is required for 4.16 and later kernels,
and because of that, it would obviate the need to create the
need for a RHEL-ALT-7.6.Z branch of the crash utility.  Ideally
the RHEL7.6 version could be used for both RHEL7 and RHEL-ALT-7
instead of maintaining a separate RHEL-ALT-7 branch.

It is far more efficient, and far safer, to rebase the crash 
package than to attempt to selectively backport individual patches.
As the owner and upstream maintainer, one of my primary goals is,
and always has been, to maintain backwards-compatibility whenever 
new fixes or features are applied.  The risk of regression is 
less with a rebase than it would be with selective backports.

It should be noted that nothing goes into the upstream version 
without my approval.  I perform all my testing on Fedora and RHEL
kernel versions, where each individual change is meticulously 
tested against a sample set of RHEL3, RHEL4, RHEL5, RHEL6, RHEL7,
Fedora, and RHEL-ALT-7 kernels.

Details regarding recent fixes, features and enhancements can be found in:

  http://people.redhat.com/anderson/crash.changelog.html


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

crash-7.2.0-6.el7


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 6 errata-xmlrpc 2018-10-30 10:30:21 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-2018:3142