From: Mimi Zohar <zohar@linux.ibm.com>
To: Rob Landley <rob@landley.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefan Berger <stefanb@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org,
"Milton D. Miller II" <mdmii@outlook.com>,
Jeff Layton <jlayton@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Jim Cromie <jim.cromie@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
initramfs <initramfs@vger.kernel.org>
Subject: Re: [RFC PATCH] rootfs: Use tmpfs for rootfs even if root= is given
Date: Thu, 02 Nov 2023 07:56:19 -0400 [thread overview]
Message-ID: <2061e234534c4d406b92999b9ca5c7f2194e3c9d.camel@linux.ibm.com> (raw)
In-Reply-To: <6dae6aa6-e6c6-89d6-f9d7-7563708f7662@landley.net>
On Wed, 2023-11-01 at 06:35 -0500, Rob Landley wrote:
> 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, the patch set wasn't upstreamed, but it certainly wasn't ignored.
There were multiple comments.
Can you at least re-post "[PATCH 5/5] fix rootfstype=tmpfs" after
addressing the checkpatch.pl complaints?
--
thanks,
Mimi
parent reply other threads:[~2023-11-02 11:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6dae6aa6-e6c6-89d6-f9d7-7563708f7662@landley.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2061e234534c4d406b92999b9ca5c7f2194e3c9d.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=initramfs@vger.kernel.org \
--cc=jim.cromie@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdmii@outlook.com \
--cc=rob@landley.net \
--cc=sam@ravnborg.org \
--cc=stefanb@linux.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).