linux-kernel - Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels

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: <20160327083159.GA32241@pd.tnic>
Date:	Sun, 27 Mar 2016 10:31:59 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	LKML <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>
Subject: Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch
 levels

On Sat, Mar 26, 2016 at 08:31:57PM -0300, Henrique de Moraes Holschuh wrote:
> This patchset looks like it is pretty much a requirement for any distro that
> ships AMD microcode updates...  Maybe the two commits should be sent to
> -stable, now that they have seen lots of testing in mainline 4.4.x as well
> as SuSE kernels?

I wouldn't say lots... :)

Do you have any specific bug report(s) or similar in mind? Or is it more
of a "it would be wise to backport" sentiment?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.