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:	Tue, 12 Nov 2013 23:45:11 +0100
From:	Borislav Petkov <bp@...e.de>
To:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	stable@...nel.org, tglx@...utronix.de, trenn@...e.de, bp@...e.de
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86/microcode/amd: Tone down printk(), don' t
 treat a missing firmware file as an error

On Tue, Nov 12, 2013 at 01:58:00PM -0800, tip-bot for Thomas Renninger wrote:
> Commit-ID:  11f918d3e2d3861b6931e97b3aa778e4984935aa
> Gitweb:     http://git.kernel.org/tip/11f918d3e2d3861b6931e97b3aa778e4984935aa
> Author:     Thomas Renninger <trenn@...e.de>
> AuthorDate: Tue, 12 Nov 2013 17:39:43 +0100
> Committer:  Ingo Molnar <mingo@...nel.org>
> CommitDate: Tue, 12 Nov 2013 22:03:49 +0100
> 
> x86/microcode/amd: Tone down printk(), don't treat a missing firmware file as an error
> 
> Do it the same way as done in microcode_intel.c: use pr_debug()
> for missing firmware files.
> 
> There seem to be CPUs out there for which no microcode update
> has been submitted to kernel-firmware repo yet resulting in
> scary sounding error messages in dmesg:
> 
>   microcode: failed to load file amd-ucode/microcode_amd_fam16h.bin
> 
> Signed-off-by: Thomas Renninger <trenn@...e.de>
> Acked-by: Borislav Petkov <bp@...e.de>
> Cc: <stable@...nel.org>

Shouldn't that be <stable@...r.kernel.org> ?

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ