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  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:	Sun, 24 Jan 2010 15:26:09 -0800
From:	"H. Peter Anvin" <>
To:	Nigel Kukard <>
Subject: Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs

On 01/16/2010 03:12 AM, Nigel Kukard wrote:
> Generating a initramfs with the following, one of about 30Mb, one of 77Mb.
> find . | cpio -o -H newc > ../initramfs.cpio
> Only difference is adding of more files to the 77Mb image.
> It makes no difference if its compiled into kernel or used as initrd.
> Compression types makes no difference either.
> Tested on>2.6.33-rc4 , all fail with the below.
> The 30Mb initramfs loads fine, the 77Mb image throws the following...

What are the exact compressed and uncompressed files (or is that an
uncompressed initramfs)?

Also, you're describing how to reproduce this with Qemu, but have you
tried with other bootloaders?  Which version of Qemu (some versions of
the Qemu bootloaders had a lot of problems.)


H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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