Re: [PATCH RESEND 00/62] initrd: remove classic initrd support
Nicolas Schichan <[email protected]> Fri, 19 Sep 2025 17:24:48 +0200
| Newsgroups | org.kernel.vger.initramfs,dev.linux.lists.loongarch,dev.linux.lists.patches,org.infradead.lists.linux-riscv,org.infradead.lists.linux-snps-arc,org.infradead.lists.linux-um,org.kernel.vger.linux-acpi,org.kernel.vger.linux-alpha,org.kernel.vger.linux-api,org.kernel.vger.linux-arch,org.kernel.vger.linux-block,org.kernel.vger.linux-csky,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-efi,org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-hexagon,org.kernel.vger.linux-kernel,org.kernel.vger.linux-m68k,org.kernel.vger.linux-mips,org.kernel.vger.linux-openrisc,org.kernel.vger.linux-parisc,org.kernel.vger.linux-s390,org.kernel.vger.linux-sh,org.kernel.vger.sparclinux,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <CAHNNwZAzecVcJXZmycX063-=p-M5jVkfStfgYVKJruOFo7y9zg@mail.gmail.com> |
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