Re: Bug#865153: reportbug: please include kernel taint flags
Hello Adam,
On Mon, Jun 19, 2017 at 12:48 PM Adam Borowski <kilobyte@angband.pl> wrote:
>
> Package: reportbug
> Version: 7.1.7
> Severity: wishlist
>
> Hi!
> The "System Information" part of reportbug's output doesn't currently
> mention the kernel's taint state. A bunch of these flags show that
> something on the system is going pretty badly, thus they're definitely
> of interest to someone reading such a bug report.
>
> The state can be read via /proc/sys/kernel/tainted which provides a decimal
> integer value, with bits meaning the following:
>
> 'P', /* TAINT_PROPRIETARY_MODULE */
> 'F', /* TAINT_FORCED_MODULE */
> 'S', /* TAINT_CPU_OUT_OF_SPEC */
> 'R', /* TAINT_FORCED_RMMOD */
> 'M', /* TAINT_MACHINE_CHECK */
> 'B', /* TAINT_BAD_PAGE */
> 'U', /* TAINT_USER */
> 'D', /* TAINT_DIE */
> 'A', /* TAINT_OVERRIDDEN_ACPI_TABLE */
> 'W', /* TAINT_WARN */
> 'C', /* TAINT_CRAP */
> 'I', /* TAINT_FIRMWARE_WORKAROUND */
> 'O', /* TAINT_OOT_MODULE */
> 'E', /* TAINT_UNSIGNED_MODULE */
> 'L', /* TAINT_SOFTLOCKUP */
> 'K', /* TAINT_LIVEPATCH */
this seems to be defined at
https://github.com/torvalds/linux/blob/master/include/linux/kernel.h#L549
which saw 2 lines added 2 months ago, and one 7 months ago (ok it's
not much, as previous changes were 4 years ago, but still since you
can install a custom kernel in stable, it means reportbug will not be
able to report correct information). i'm kinda at uneasy to add the
decoding of the bit string in reportbug if this will change often.
i think it would be ok to have an external tool that could produce the
tainted information parsing the header files and the tainted file, and
then include this tool output in reportbug systems information
section.
adding debian-kernel@l.d.o to gather some of their insight on the matter too
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
Reply to: