linux-kernel - Re: [PATCH] DMI: log system, BIOS, and board information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Sep 2010 22:26:23 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] DMI: log system, BIOS, and board information

On Wed, 29 Sep 2010 12:24:02 -0600
Bjorn Helgaas <bjorn.helgaas@...com> wrote:

> 
> Put basic system information in the dmesg log.  There are lots of dmesg
> logs on the web, and it would be useful if they contained this information
> for debugging platform problems.
> 
> DMI often doesn't supply a board name, but I assume the others are pretty
> standard.

You need to filter the characters before printing them in the log. Some
platforms contain binary garbage.

So NAK.

It's also the wrong thing in most cases because the key data is in sysfs
so your bug capturing tool can collect it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/