linux-kernel - Re: large initramfs causes h/w reset after decompressing

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E1F86AE.9090903@zytor.com>
Date:	Thu, 14 Jul 2011 17:15:42 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"John Z. Bohach" <jzb2@...orsyst.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: large initramfs causes h/w reset after decompressing

On 07/14/2011 04:35 PM, John Z. Bohach wrote:
>>> But excuse my ignorance, I don't see the relevance of your
>>> question...the initramfs is part of the kernel itself...I simply
>>> load the kernel bzImage (all 890 MB) and that's where its all
>>> at...this is _not_ an initrd.
>>
>> Ah, interesting.  You didn't say that.  That does change some
>> things... I would not at all be surprised if the kernel decompressor
>> doesn't handle that very well...
>>
> 
> Sorry, I thought initramfs would be clear on its own that its not 
> initrd, but I guess some people do use it interchangeably.  Anyway, I 
> have some experience in programming, so is there anything you could 
> suggest that I might tweak to test your theory on the decompressor?  Or 
> would this be more of a kernel VM allocator issue?  Also, would 
> ramdisk_size have any bearing on this?
> 

initramfs can be built in or loaded via the initrd protocol.

Anyway, it's hard to say for sure what to look for, but the first thing
is to try to "fence" the problem... that is, establish the latest point
which is successfully crossed and the earliest point which is not.

	-hpa

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