linux-kernel - Re: [PATCH] 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]

Message-ID: <52D81DB5.7000608@amd.com>
Date:	Thu, 16 Jan 2014 11:58:13 -0600
From:	Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
To:	Borislav Petkov <bp@...en8.de>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
	Kim Naru <kim.naru@....com>,
	Sherry Hurwitz <sherry.hurwitz@....com>
Subject: Re: [PATCH] x86, CPU, AMD: Add workaround for family 16h, erratum
 793

On 1/14/2014 2:38 PM, Borislav Petkov wrote:
> Before you go and do that, just ask internally whether those 
> workarounds are being delivered with AGESA instead. We don't want to 
> have a fix in the kernel for *every* erratum if it can be helped. 
> We're making an exception for this one because it can freeze the core 
> just by executing a locked insn which can be done even in userspace. 

Ok, So looks like workaround for E776 went in early, so it's probably 
safe to assume all BIOSes will have the fix.
The workaround for E792 was checked in this month and *will* be picked 
up by BIOS later..

We might want to still have a software fix for this just in case someone 
uses older BIOSes..

> For future AMD patches, make sure to almost always use tip master, 
> i.e. git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git#master 
> to base your work off of. 

I shall spin a patch on top of tip and send it out soon

Thanks,
-Aravind.

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