Bug 1993225

Summary:	abrt fails to parse Call Trace in RHEL 8 vmcore
Product:	Red Hat Enterprise Linux 8	Reporter:	James Hartsock <hartsjc>
Component:	abrt	Assignee:	Michal Fabik <mfabik>
Status:	CLOSED ERRATA	QA Contact:	Martin Kyral <mkyral>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.4	CC:	mfabik, mkyral, msrb, mzidek
Target Milestone:	beta	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	abrt-2.10.9-23.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-16 08:42:01 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 James Hartsock 2021-08-12 15:11:40 UTC

Description of problem:
The call traces in vmcore-dmesg output do not include the memory addresses, which means abrtd doesn't recognise the stack trace.

Version-Release number of selected component (if applicable):
abrt-2.10.9-10.el8

How reproducible:
Very

Steps to Reproduce:
1. Collect vmcore from RHEL 8 (or any kernel v4.10 or newer)
2. Process kdump's vmcore-dmesg output with abrt

Actual results:
Fails to identify the OOPS / calltrace from kernel ring buffer output (ie. vmcore-dmesg)

Expected results:
Should work like did in RHEL 7, and properly identify the Call Trace:

Additional info:

Per upstream, looking for "[<ffffffffa006c156>]" style address
  https://github.com/abrt/abrt/blob/master/src/lib/kernel.c#L478-L48

However, this address was removed from kernel upstream back in 2016 (looks to be part of v4.10)
  x86/dumpstack: Remove kernel text addresses from stack dump
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5e5ce545f20

Comment 19 errata-xmlrpc 2023-05-16 08:42:01 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 (abrt 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-2023:2897