On Sun, 2018-06-17 at 15:17 -0400, Sandro Tosi wrote:
> 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.
[...]
> 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
Kernel taint flags were introduced in 2002 and since then no flags have
ever been deleted or renumbered (although one flag was renamed to be
more general). So I think that this is quite a stable interface. For
any new and unknown flag, you could report it by number e.g. print
8393216 (bits 9, 12, 23 set) as "W O [23]".
Ben.
--
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy others.
Attachment:
signature.asc
Description: This is a digitally signed message part