linux-kernel - Re: [tip:x86/urgent] x86, cpu, amd: Add workaround for family 16h, erratum 793

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, 15 Jan 2014 20:11:14 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...nel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
CC:	Borislav Petkov <bp@...e.de>, linux-kernel@...r.kernel.org,
	aravind.gopalakrishnan@....com, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86, cpu, amd: Add workaround for family 16h,
 erratum 793

On 01/15/2014 10:38 AM, Ingo Molnar wrote:
> 
> Right, the fact that most of our MSR accesses today are 
> crash-on-failure, which happens to trigger crashes on a regular 
> schedule, where most of the crashes are 'harmless' situation except 
> that they crash the systems for good.
> 
> So I think defaulting to soft failures is the right approach.
> 

Well, as I said, as long as people don't start doing:

	BUG_ON(msr_read(...))

... 'cuz that's just silly.  Also, on 64 bits the code generated by
going from 2x32 bits to 1x64 and sometimes back can add up (on 32 bits
there is no difference.)

	-hpa


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