All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Rob Landley <rob@landley.net>,
	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>,
	Mimi Zohar <zohar@linux.ibm.com>
Subject: Re: [RFC PATCH] rootfs: Use tmpfs for rootfs even if root= is given
Date: Wed, 1 Nov 2023 15:28:00 +0100	[thread overview]
Message-ID: <2023110159-rasping-stature-af8d@gregkh> (raw)
In-Reply-To: <a8693232-431e-4840-a020-cd83c162446e@linux.ibm.com>

On Wed, Nov 01, 2023 at 10:16:37AM -0400, Stefan Berger wrote:
> 
> 
> On 11/1/23 07:35, 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/
> 
> Everyone,
> I now responded to Rob's patch over here:
> https://lkml.org/lkml/2023/11/1/333

Note, we can't do anything with lkml.org links, they don't even work at
times, please always use lore.kernel.org

Also, one patch out of a longer series also will not work as we can't
pick it up from there either.

Can someone resend it, as a stand-alone patch, with the proper people
 cc:ed and then we can handle that.  You all know this...

 thanks,

 greg k-h

> 
> 
> > 
> > Rob

  reply	other threads:[~2023-11-01 14:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 15:44 [RFC PATCH] rootfs: Use tmpfs for rootfs even if root= is given Stefan Berger
2023-10-31 16:56 ` Greg Kroah-Hartman
     [not found]   ` <b035a00f-865a-453c-bb27-0916aada0594@linux.ibm.com>
2023-10-31 20:33     ` H. Peter Anvin
2023-10-31 21:02       ` Stefan Berger
2023-11-01 11:35   ` Rob Landley
2023-11-01 12:11     ` Stefan Berger
2023-11-01 14:48       ` Rob Landley
2023-11-01 14:16     ` Stefan Berger
2023-11-01 14:28       ` Greg Kroah-Hartman [this message]
2023-11-01 14:31         ` Mimi Zohar
2023-11-02 11:56     ` Mimi Zohar

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=2023110159-rasping-stature-af8d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --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 \
    --cc=zohar@linux.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.