linux-kernel - Re: [PATCH v2] 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:	Mon, 4 Oct 2010 20:45:29 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH v2] DMI: log system, BIOS, and board information

On Mon, Oct 04, 2010 at 04:19:26PM -0700, Andrew Morton wrote:
> On Thu, 30 Sep 2010 10:49:05 -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.
> > 
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@...com>
> > ---
> > 
> >  drivers/firmware/dmi_scan.c |   35 ++++++++++++++++++++++++++++++++++-
> >  1 files changed, 34 insertions(+), 1 deletions(-)
> > 
> > 
> > diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
> > index b3d22d6..d625e53 100644
> > --- a/drivers/firmware/dmi_scan.c
> > +++ b/drivers/firmware/dmi_scan.c
> > @@ -2,6 +2,7 @@
> >  #include <linux/string.h>
> >  #include <linux/init.h>
> >  #include <linux/module.h>
> > +#include <linux/ctype.h>
> >  #include <linux/dmi.h>
> >  #include <linux/efi.h>
> >  #include <linux/bootmem.h>
> > @@ -361,6 +362,36 @@ static void __init dmi_decode(const struct dmi_header *dm, void *dummy)
> >  	}
> >  }
> >  
> > +static const char * __init dmi_printable_system_info(int field)
> > +{
> > +	const char *info, *p;
> > +
> > +	info = dmi_get_system_info(field);
> > +	if (!info)
> > +		return NULL;
> > +
> > +	for (p = info; *p; p++)
> > +		if (!isprint(*p))
> > +			return "<...>";
> > +
> > +	return info;
> > +}
> 
> So if the string contains any non-printable character, we suppress the
> whole string.
> 
> Is that the best thing to do?  Would it be better to present the
> oddball character as \xNN or such?

I would definitely prefer to do that, but that would mean allocating
memory, and this happens so early that it looked like it would be
more trouble than it's worth.  I'm not saying I couldn't be convinced,
though.

Bjorn
--
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/