linux-kernel - Re: [PATCH 1/3] mce: Add a msg string to the MCE tracepoint

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:	Thu, 01 Mar 2012 16:54:58 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	"Luck, Tony" <tony.luck@...el.com>
CC:	Borislav Petkov <bp@...64.org>, Ingo Molnar <mingo@...e.hu>,
	EDAC devel <linux-edac@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] mce: Add a msg string to the MCE tracepoint

Em 01-03-2012 15:58, Luck, Tony escreveu:
>> Query from where? (And pls don't tell me DMI tables. :-))
> 
> Sorry - but DMI is all we've got.  We need to start using it, and have
> people report bugs when it is wrong. Then it might get better. Linux
> has had some success in shaming BIOS writers with:
> 
>  printk("Your BIOS is buggy ...")
> 
> Our biggest problem here is the life-cycle ... by the time Linux
> users start seeing these problems, the BIOS people have already
> moved on to the next generation system.
> 
> BUT - if Linux wants to play in RAS space - we need this to be
> right - and to do that we need SMBIOS (DMI) bugs to be regarded as
> priority #1.

This approach may work, if we put enough pressure on BIOS bugs. It is
a way better for us than the way EDAC took: adding a sysfs node for some
util to write the labels there. Yet, they did that because a lot of DMI 
tables were wrong.

Well, we can always have a buggy-BIOS quirk file shaming the BIOS writers,
while providing the right values to the end users, as we got bugs reporting
issues with certain motherboards and/or manufacturers.

Regards,
Mauro.
--
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/