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:
satyr does not find any reliable frame for hashing and generates the hash value from empty string. ABRT uses the hash value to identify duplicates in Bugzilla, so it means that all unreliable oopses are reported as a single Bugzilla bug. However, that koopses should not be reported at all. In order to fix this issue, satyr must return NULL from the hashing function for unreliable koopses.

Version-Release number of selected component (if applicable):
abrt-2.1.11-12.el7

Additional info:
Upstream commit https://github.com/abrt/satyr/commit/d818117a985ed5bdd00eafbc6ef9ce3f9ec54c58 fixes this bug.

*** Bug 1142342 has been marked as a duplicate of this bug. ***

The upstream patch includes a test case:
https://github.com/abrt/satyr/commit/d818117a985ed5bdd00eafbc6ef9ce3f9ec54c58

ABRT tests satyr's ability to recognize an unreliable oops in 'Drop unreliable OOPS' phase of 'oops-processing' integration test[1] ('oops_no_reliable_frame' file [2]).

1: https://github.com/abrt/abrt/tree/master/tests/runtests/oops-processing
2: https://github.com/abrt/abrt/blob/master/examples/oops_no_reliable_frame.test

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://rhn.redhat.com/errata/RHBA-2015-0556.html