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  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:	Mon, 11 Aug 2014 07:51:34 -0700
From:	"H. Peter Anvin" <>
To:	Henrique de Moraes Holschuh <>,
	Borislav Petkov <>,
	Fenghua Yu <>
Subject: Re: BUG: early intel microcode update violating alignment rules

On 08/09/2014 04:19 PM, Henrique de Moraes Holschuh wrote:
> This will only happen when the microcode update file data inside the early
> initramfs archive is not 16-byte aligned.  Unfortunately, the cpio format
> used in the early initramfs aligns the member file data just to 4-byte
> boundaries.
> Is there a way to fix this in the kernel for the BSP?  We already have
> several microcode updates that are >16KiB in size and they seem to be
> getting bigger and bigger, so doing it on the stack is out.
> Maybe there is a 64KiB scratch area that could be used just to get the BSP
> microcode update done?  vmalloc isn't available that early, but it can be
> used to fix the issue for the APs.

We could put a buffer in the initdata region (we really could use an
initbss region!) or in the brk.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists