Include kernel tainted state in JSON output

Did this recently show up? I recall sending a report with an out-of-tree panel driver for an msm device and intend to send many more when everything has landed in -next and is readily available from an untainted Linux kernel release. Holding back on those even though it'll still take a long time to get finalized and propagate...

EDIT: Such a thing does not cause tainted to become non-zero.

Hm, you mean out-of-tree doesn't trigger tainted? That's surprising, there is specifically a flag for it: "externally-built ("out-of-tree") module was loaded" in https://www.kernel.org/doc/html/latest/admin-guide/tainted-kernels.html

Although yeah, a -next kernel (or a kernel built from any source) will not be tainted. The only way to detect such kernels is to guess by the version string AFAIK.

Yeah, the kernel is built with all modules builtin from the same kernel source. Indeed, you can only piece it out from the version string (and that is already available in the current dump), but that should be enough for users of drmdb to read.

Also note, drmdb currently does nothing in particular with the tainted status and version string. It would be nice to add a UI for it.

Looks like the version string is available for the reader at least?

https://drmdb.emersion.fr/snapshots/3d85ca357797

Driver: msm (MSM Snapdragon DRM) version 1.10.0 (20130625) on Linux 6.4.0-SoMainline-00006-gbb5819fd6b81

On another note, in https://drmdb.emersion.fr/devices, where's the Vendor and Name field filled in?

These come from hwdata.