Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The rhel-8.1.0 errata version of the crash utility, which is based
upon crash-7.2.3, should be rebased to the current upstream version,
currently at version crash-7.2.5, and soon to be crash-7.2.6. 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 rhel-8.0.0 version, which is based upon crash-7.2.3 plus
a hodge-podge set of backports. For example, the upstream version
contains support for the new /proc/kcore VMCOREINFO ELF note, which
will be introduced in the rhel-8.1.0 kernel, support for the
upstream kernel replacement of radix trees with the new xarray facility,
which affects several crash commands, and several fixes for other
crash commands. Furthermore, the crash-7.2.6 version, as of yet
unreleased, will have support for ARM64 52-bit kernel virtual address
space that will be introduced in the rhel-8.1.0 kernel.
Furthermore, since Linux 4.19 and later kernels require crash-7.2.5,
the current rhel-8.0.0 version of crash cannot be utilized with Linux
5.0.0-based RHEL ARK kernels.
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, RHEL-ALT-7, and RHEL ARK 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.3-18.el8
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
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:3349