+++ This bug was initially created as a clone of Bug #1214730 +++

Description of problem:

In abrt oops data, the kernel is reports as tainted, though this is a fresh 7.1 install with nothing else added.


dmesg:[ 7019.437238] CPU: 1 PID: 14620 Comm: kworker/u17:0 Not tainted 3.10.0-229.1.2.el7.x86_64 #1
not-reportable:A kernel problem occurred, but your kernel has been tainted (flags:GW). Kernel maintainers are unable to diagnose tainted reports.

$ cat kernel_tainted_long
Proprietary module has not been loaded.
Taint on warning.

$ cat kernel_tainted_short
GW

From the backtrace:

CPU: 1 PID: 14620 Comm: kworker/u17:0 Tainted: G        W   --------------   3.10.0-22
9.1.2.el7.x86_64 #1


Version-Release number of selected component (if applicable):

7.1 (3.10.0-229.1.2.el7.x86_64)


How reproducible:

- Unknown

Expected results:

- kernel not reported to be tainted if it is truly not.


--- Additional comment from Julius Milan on 2017-05-12 08:52:49 EDT ---

In opening message is written:
"In abrt oops data, the kernel is reports as tainted, though this is a fresh 7.1 install with nothing else added."

this is not in contradiction with content of not-reportable:
"A kernel problem occurred, but your kernel has been tainted (flags:GW). Kernel maintainers are unable to diagnose tainted reports."

That kernel is tainted, doesn't imply something had to be loaded into it, however I agree that this message can be confusing in this situation.

I propose to extend the not-reportable message to this form:

"
A kernel problem occurred, but your kernel has been tainted (flags:GW). Kernel maintainers are unable to diagnose tainted reports.
Kernel may become tainted for one of following reasons:
* The use of a proprietary (or non-GPL-compatible) kernel module.
* The use of staging drivers, which are part of the kernel source code but are not fully tested.
* The use of out-of-tree modules that are not included with the Linux kernel source code.
* Forcible loading or unloading of a kernel module (such as forcibly inserting a module not built for the current version of the kernel).
* The use of an SMP (multiprocessor) kernel on certain unsupported uniprocessor CPUs, primarily older AMD Athlon processors.
* Overriding of the ACPI DSDT, sometimes needed to correct for power-management bugs.
* Certain critical error conditions, such as machine check exceptions and kernel oopses.
* Certain serious bugs in the system firmware (BIOS, UEFI) which the kernel must work around.
"