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: <20160327154748.GD32241@pd.tnic>
Date:	Sun, 27 Mar 2016 17:47:48 +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 Sun, Mar 27, 2016 at 09:32:18AM -0300, Henrique de Moraes Holschuh wrote:
> So, it is really a bit of both: I had several "it doesn't work" type of
> reports for both AMD and Intel over the years, and most often people won't
> come back to the initial bug report,

Can you CC me on stuff like that too, please.

But yeah, unfortunately, bug reporters disappear and it is kinda hard to
debug an issue then. Which is sad. :-\

But ok. I'll put it on my TODO, will get to it eventually. Unless you
beat me to it... :)

-- 
Regards/Gruss,
    Boris.

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