linux-kernel - Should corrected machine check errors still taint the kernel?

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1301443098.5867.34.camel@w-amax.beaverton.ibm.com>
Date:	Tue, 29 Mar 2011 16:58:17 -0700
From:	Max Asbock <masbock@...ux.vnet.ibm.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Cc:	Andi Kleen <ak@...ux.intel.com>
Subject: Should corrected machine check errors still taint the kernel?

I noticed that corrected machine check errors taint the kernel. And it
looks like they have done that forever.

Is that still the right thing to do?

The comment in add_taint() says:
"Can't trust the integrity of the kernel anymore."

I don't think that's necessarily the case after seeing a corrected
memory error.

thanks,
Max 

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