Bug 1068767

Summary:	hash collision is likely for X backtrace (satyr does not filter out enough names)
Product:	[Fedora] Fedora	Reporter:	Alois Mahdal <amahdal>
Component:	satyr	Assignee:	Martin Milata <mmilata>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	abrt-devel-list, dvlasenk, iprikryl, jfilak, mmilata, mtoman, rh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	satyr-0.14-1.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-09 21:48:29 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 Alois Mahdal 2014-02-21 20:29:22 UTC

I encountered Xorg crash caused by qxl driver.  As the same time, there was already existing bug report from another crash from another cirrus driver.  Instead of creating new bug, ABRT added comment to the existing cirrus bug.

This was caused by the fact that ABRT did not filter out all unrelated function names from the data the abrt_hash is computed from.  Therefore two different backtraces (having only the error handling really common) resulted in same abrt_hash.


Version-Release number of selected component (if applicable):
abrt-2.1.12-2.fc20.x86_64


If you want to see the backtraces:

  * attachment 862417 [details] is for the "cirrus" bug 1064466
  * attachment 865735 [details] is for the "qxl" bug 1067709

~

The part of stack that is common:

#0  0xXXXXXXXXXXXXXXXX in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#0  0xXXXXXXXXXXXXXXXX in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0xXXXXXXXXXXXXXXXX in __GI_abort () at abort.c:90
#2  0xXXXXXXXXXXXXXXXX in OsAbort () at utils.c:1328
#3  0xXXXXXXXXXXXXXXXX in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:1097
#4  0xXXXXXXXXXXXXXXXX in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:1141
#5  0xXXXXXXXXXXXXXXXX in AbortServer () at log.c:770
#6  0xXXXXXXXXXXXXXXXX in FatalError (f=f@entry=0x5c6648 "Caught signal %d (%s). Server aborting\n") at log.c:911
#7  0xXXXXXXXXXXXXXXXX in OsSigHandler (signo=11, sip=<optimized out>, unused=<optimized out>) at osinit.c:147
#8  <signal handler called>

Comment 1 Martin Milata 2014-02-24 11:51:17 UTC

Patch submitted upstream: https://github.com/abrt/satyr/pull/157

Comment 2 Martin Milata 2015-02-24 13:53:13 UTC

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