linux-kernel - Re: Possible bug in initramfs RAM handling

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] [day] [month] [year] [list]

Date:	Wed, 21 Jan 2015 15:38:32 -0500
From:	"Lennart Sorensen" <lsorense@...lub.uwaterloo.ca>
To:	Tobias Powalowski <tobias.powalowski@...glemail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Possible bug in initramfs RAM handling

On Mon, Jan 12, 2015 at 05:20:31PM +0100, Tobias Powalowski wrote:
> I have a weird bug here with initramfs,
> I have big initramfs files around 150MB zipped, 400MB extracted.
> I suppose the needed RAM to boot this setup should be around:
> 150MB zipped initramfs+ 400MB extracted initramfs + 5MB kernel image.
> Our distro kernel has tmpfs support, booting this setup without kernel
> parameter needs around 1000MB RAM to boot.
> Using rootfstype=ramfs makes it work with around 600MB RAM.
> 
> Is this a bug in kernel code?
> Shouldn't both types not use the same amount of RAM?
> I used kernel 3.18.2 at the moment but issue is reproducable with 3.15 too.

tmpfs defaults to size=50%, meaning it can not use more than half the
ram in the system.  Could that be your problem?

After all if the extracted size is 400MB, and tmpfs limit is 50% of ram,
that alone means it must have at least 800MB of ram to allow extracting
to tmpfs.  Add in the 150MB compressed size and you are close to your
1000MB value.  ramfs probably has no such limit and hence you can get
by with 600MB.

Maybe 'rootflags=size=90%' or something like that would help.
Not entirely sure if that is the correct syntax.

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