Bug 593084

Summary: abrt shouldn't file bugs if the kernel is tainted
Product: [Fedora] Fedora Reporter: Matthew Garrett <mjg>
Component: abrtAssignee: Denys Vlasenko <dvlasenk>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anton, dvlasenk, iprikryl, jfeeney, jmoskovc, kklic, mnowak, npajkovs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-10 14:12:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthew Garrett 2010-05-17 19:19:03 UTC 
Kernel traces or warnings generated when the kernel is already tainted are highly likely to be a consequence of whatever caused the taint. Automatically filing these bugs consumes disproportionate developer time as a result. It would be preferable if abrt only filed bugs from untainted kernels.
Comment 1 Denys Vlasenko 2011-05-10 14:12:51 UTC 
Fixed in git:

    if (tainted_str && analyzer
        && (strcmp(analyzer, "Kerneloops") == 0)
    ) {
        unsigned long tainted = xatoi_positive(tainted_str);
        const char *tainted_warning = tainted_string(tainted);
        if (tainted_warning)
            strbuf_append_strf(buf_summary, ": TAINTED %s", tainted_warning);
    }