linux-kernel - Re: [PATCH]: mce: don't print "human readable" message for corrected errors

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:	Tue, 12 Apr 2011 16:15:38 -0400
From:	Prarit Bhargava <prarit@...hat.com>
To:	"Luck, Tony" <tony.luck@...el.com>
CC:	Borislav Petkov <bp@...en8.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"dzickus@...hat.com" <dzickus@...hat.com>,
	"mstowe@...hat.com" <mstowe@...hat.com>,
	"dnelson@...hat.com" <dnelson@...hat.com>
Subject: Re: [PATCH]: mce: don't print "human readable" message for corrected
 errors


> We are also setting TAINT_MACHINE_CHECK for corrected errors - perhaps
> this made sense when systems were small and machine checks were rare and
> scary.  But I think we need to start working with the reality that
> corrected errors are normal events.
>
>   

It still makes sense for small lt 1TB systems, IMO.  But ... maybe a
flag of some sort is necessary to stop the TAINTing for systems larger
than that.  The CEs may point to something going wrong on a system.  CEs
in theory become UCEs eventually, right?

>From a OS point of view, we would like to know that there is flaky HW on
the system.

/me knows this is going to turn into a PFA discussion in 4 ... 3 ... 2
....   ;)

P.

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