Bug 724838 - don't file kernel bugs if "tainted: B" is set.
Summary: don't file kernel bugs if "tainted: B" is set.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nikola Pajkovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-21 23:59 UTC by Dave Jones
Modified: 2015-01-04 22:31 UTC (History)
10 users (show)

Fixed In Version: abrt-2.0.3-5.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-04 02:28:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Jones 2011-07-21 23:59:17 UTC
If something has corrupted memory, we typically see a whole bunch of things start crashing. This leads to situations where abrt files a lot of bugs, even though most of them are just fallout from the first.

an example: bugs 710925 710930 710932 710933 710935 710942 710948 710955 710956 are all the same crash. The traces and addresses are different, but 'something scribbled over memory' is the root cause here. Sadly out of all those bugs, we actually somehow missed the first crash which is the most relevant one. (That one would have not had the 'Tainted: G B' text)

(as an aside, look at the time: field on the text abrt filed. somehow they got filed out of order, which made things even more confusing).

All those bugs happened across three different days, but some of the timestamps show that they were very close together, so at least half of these could have not been filed.  The only useful bugs out of that list are the untainted ones.

Comment 1 Nikola Pajkovsky 2011-07-22 06:25:08 UTC
Let's make proper fix. What kind of tainted flags are for kernel guys relevant?

Comment 2 Dave Jones 2011-07-22 17:21:09 UTC
Actually, if you fix 708534, so that abrt parses the oops text instead of relying on /proc/sys/kernel/tainted, we could just say "don't file any bugs that are tainted".

But because we're using the sysctl, we're always going to show 'G' 'B' 'W' 'D', which we only care for the first instance.

Any other flags, we can't do anything about (machine checks, bad bios, proprietary modules etc).
If abrt wants to pop up a dialog explaining that, that's fine, but explain that filing a bug would be pointless.

Comment 3 Nikola Pajkovsky 2011-10-05 14:57:46 UTC
fix has landed the git

Comment 4 Fedora Update System 2011-10-07 12:09:26 UTC
abrt-2.0.4.981-3.fc16,libreport-2.0.6-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/abrt-2.0.4.981-3.fc16,libreport-2.0.6-2.fc16

Comment 5 Fedora Update System 2011-10-07 14:55:01 UTC
abrt-2.0.3-5.fc15,libreport-2.0.4-4.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.3-5.fc15,libreport-2.0.4-4.fc15

Comment 6 Fedora Update System 2011-10-09 06:53:38 UTC
Package abrt-2.0.3-5.fc15, libreport-2.0.4-4.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.3-5.fc15 libreport-2.0.4-4.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-14015
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2011-10-19 04:41:21 UTC
abrt-2.0.4.981-3.fc16, libreport-2.0.6-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2011-12-04 02:28:20 UTC
abrt-2.0.3-5.fc15, libreport-2.0.4-4.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.