[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6dae6aa6-e6c6-89d6-f9d7-7563708f7662@landley.net>
Date: Wed, 1 Nov 2023 06:35:37 -0500
From: Rob Landley <rob@...dley.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stefan Berger <stefanb@...ux.ibm.com>
Cc: linux-kernel@...r.kernel.org,
"Milton D. Miller II" <mdmii@...look.com>,
Jeff Layton <jlayton@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Jim Cromie <jim.cromie@...il.com>,
Sam Ravnborg <sam@...nborg.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
"H. Peter Anvin" <hpa@...or.com>, Mimi Zohar <zohar@...ux.ibm.com>
Subject: Re: [RFC PATCH] rootfs: Use tmpfs for rootfs even if root= is given
On 10/31/23 11:56, Greg Kroah-Hartman wrote:
> On Tue, Oct 31, 2023 at 11:44:17AM -0400, Stefan Berger wrote:
>> rootfs currently does not use tmpfs if the root= boot option is passed
>> even though the documentation about rootfs (added in 6e19eded3684) in
>> Documentation/filesystems/ramfs-rootfs-initramfs.rst states:
>>
>> If CONFIG_TMPFS is enabled, rootfs will use tmpfs instead of ramfs by
>> default. To force ramfs, add "rootfstype=ramfs" to the kernel command
>> line.
>
> At this point in time, is there even any difference between ramfs and
> tmpfs anymore? Why would you want to choose one over the other here?
I submitted a patch to fix this to the list multiple times, which got ignored as
always. Most recently here:
https://lore.kernel.org/lkml/8244c75f-445e-b15b-9dbf-266e7ca666e2@landley.net/
Rob
Powered by blists - more mailing lists