linux-kernel - Re: [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store initrd's start

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: <20160725150701.GA19496@nazgul.tnic>
Date:	Mon, 25 Jul 2016 17:07:01 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Nicolai Stange <nicstange@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store
 initrd's start

On Mon, Jul 25, 2016 at 04:16:41PM +0200, Nicolai Stange wrote:
> And a third one, more of a sidenote: I've seen a comment somewhere that
> blobs.start is set to 0 in the builtin case. However, I was unable to
> find this initialization in the original code.

Hint: struct ucode_blobs blobs is declared static.

-- 
Regards/Gruss,
    Boris.

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