linux-kernel - RE: Question about unpacking large initramfs (>2G)

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]

Message-ID: <a6dddd70d2844e438c2e6c205fa41b7d@AcuMS.aculab.com>
Date: Sun, 10 Mar 2024 19:43:18 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Nazerke Turtayeva' <nturtayeva@...b.edu>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: RE: Question about unpacking large initramfs (>2G)

From: Nazerke Turtayeva
> Sent: 09 March 2024 03:11
> 
> Recently I was testing LLMs for RISC-V on Linux plus Buildroot plus
> OpenSBI and Spike ISA Simulator. Nevertheless, given my rootfs end up
> being pretty large, 3.6GB at the moment, my linux boot falls short
> with "Initramfs unpacking failed: write error". I was trying to debug
> this problem last week, but got confused with code complexity :(.

I'd look at removing unwanted stuff from initramfs.
For our buildroot images we delete a lot of stuff - since it
can be found in the disk image after mounting the disk /.
(Although I'm not at all sure how much of the initramfs memory
is recovered - especially without pivot_root.

One thing I have noticed on x86 is that the .ko files are
massive because they contain a lot of debug info.
(I was looking at why it took so long between the last grub
message and the first kernel one.)
Also the default build also puts all the modules into the
initramfs - even though most can be loaded from the root filesystem.

	David.

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)