linux-kernel - Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs

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: <4BA52B6F.2060402@lbsd.net>
Date:	Sat, 20 Mar 2010 20:09:19 +0000
From:	Nigel Kukard <nkukard@...d.net>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs


>>>> 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.32.3->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)?
>>>   
>>>       
>> Ok ... I revisited this, sorry for the delay, all tests done on kernel
>> 2.6.33.1
>>
>> (initramfs uploaded, link below)
>>
>> It is generated using two commands...
>> find . | cpio -o --quiet -H newc -A -O ../initramfs.cpio
>>
>> and the kernel modules are appended to this using...
>> find . | cpio -o --quiet -H newc -A -O ../initramfs.cpio
>>
>> The exact size is ..
>> % ls -la initramfs.cpio
>> -rw-r--r-- 1 nkukard nkukard 115944448 Mar 19 22:15 initramfs.cpio
>>
>>     
> How much RAM are you giving your VM?  The default for Qemu is 128 MB,
> and if you have a 110 MB initramfs it's hardly surprising that you get
> an out of memory error.

The kernel now boots where it booted for my 64bit box.

The main problem though is the instant reboots for bzip2 and lzma
compressed initramfs images. The change for printf to /usr/bin/printf
both render the sane end result when run with the same commandline being
run in the makefile, so this isn't the issue.

-N
--
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/