linux-ext4 - Re: [PATCH RESEND 00/62] initrd: remove classic initrd support

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: <CAHNNwZAzecVcJXZmycX063-=p-M5jVkfStfgYVKJruOFo7y9zg@mail.gmail.com>
Date: Fri, 19 Sep 2025 17:24:48 +0200
From: Nicolas Schichan <nschichan@...ebox.fr>
To: Askar Safin <safinaskar@...il.com>
Cc: akpm@...ux-foundation.org, andy.shevchenko@...il.com, axboe@...nel.dk, 
	brauner@...nel.org, cyphar@...har.com, devicetree@...r.kernel.org, 
	ecurtin@...hat.com, email2tema@...il.com, graf@...zon.com, 
	gregkh@...uxfoundation.org, hca@...ux.ibm.com, hch@....de, 
	hsiangkao@...ux.alibaba.com, initramfs@...r.kernel.org, jack@...e.cz, 
	julian.stecklina@...erus-technology.de, kees@...nel.org, 
	linux-acpi@...r.kernel.org, linux-alpha@...r.kernel.org, 
	linux-api@...r.kernel.org, linux-arch@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-block@...r.kernel.org, 
	linux-csky@...r.kernel.org, linux-doc@...r.kernel.org, 
	linux-efi@...r.kernel.org, linux-ext4@...r.kernel.org, 
	linux-fsdevel@...r.kernel.org, linux-hexagon@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org, 
	linux-mips@...r.kernel.org, linux-openrisc@...r.kernel.org, 
	linux-parisc@...r.kernel.org, linux-riscv@...ts.infradead.org, 
	linux-s390@...r.kernel.org, linux-sh@...r.kernel.org, 
	linux-snps-arc@...ts.infradead.org, linux-um@...ts.infradead.org, 
	linuxppc-dev@...ts.ozlabs.org, loongarch@...ts.linux.dev, mcgrof@...nel.org, 
	mingo@...hat.com, monstr@...str.eu, mzxreary@...inter.de, 
	patches@...ts.linux.dev, rob@...dley.net, sparclinux@...r.kernel.org, 
	thomas.weissschuh@...utronix.de, thorsten.blum@...ux.dev, 
	torvalds@...ux-foundation.org, tytso@....edu, viro@...iv.linux.org.uk, 
	x86@...nel.org
Subject: Re: [PATCH RESEND 00/62] initrd: remove classic initrd support

Hello,

> > When booting with root=/dev/ram0 in the kernel commandline,
> > handle_initrd() where the deprecation message resides is never called,
> > which is rather unfortunate (init/do_mounts_initrd.c):

> Yes, this is unfortunate.
>
> I personally still think that initrd should be removed.

Considering that the deprecation message didn't get displayed in some
configurations, maybe it's a bit early at the very least.

> I suggest using workaround I described in cover letter.

I'm not too keen on having an initramfs just to loop-mount
/sys/firmware/initrd, after all current kernels are able to handle the
use case just fine.

It looks like there is a lot of code calling into specific filesystems
so that the initrd code can guess the size of the file system before
copying into /dev/ram0, and I believe this is what causes the main
gripe against initrd today. What is wrong with just copying
/initrd.image using its actual size into /dev/ram0 instead of guessing
it with the help of filesystem specific code ?

> Also, for unknown reasons I didn't get your letter in my inbox.
> (Not even in spam folder.) I ocasionally found it on lore.kernel.org .

Sorry about that, When I used git-send-email yesterday to reply, the
SMTP server I used wasn't authenticated to google, so all gmail
recipients were dropped. Hopefully this work better today.

Regards,

-- 
Nicolas Schichan