mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Roberto Sassu <roberto.sassu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>,
	Jim Baxter <jim_baxter-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>,
	Eugeniu Rosca <erosca-Tbglbhd2jqSoSS7kgVBzIA@public.gmane.org>
Cc: "hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org"
	<hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	Masahiro Yamada
	<masahiroy-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Arvind Sankar <nivedita-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>,
	Mimi Zohar <zohar-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>,
	"viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org"
	<viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
	"linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-integrity-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-integrity-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"bug-cpio-mXXj517/zsQ@public.gmane.org"
	<bug-cpio-mXXj517/zsQ@public.gmane.org>,
	"zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org"
	<zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
	Silviu Vlasceanu
	<Silviu.Vlasceanu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Dmitry Kasatkin
	<dmitry.kasatkin-hv44wF8Li91hl2p70BpVqQ@public.gmane.org>
Subject: RE: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
Date: Tue, 19 Jul 2022 12:26:02 +0000	[thread overview]
Message-ID: <5b8b0bcac01b477eaa777ceb8c109f58@huawei.com> (raw)
In-Reply-To: <dc86769f-0ac6-d9f3-c003-54d3793ccfec-VoJi6FS/r0vR7s880joybQ@public.gmane.org>

> From: Rob Landley [mailto:rob@landley.net]
> Sent: Tuesday, July 19, 2022 1:51 PM
> On 7/19/22 01:55, Roberto Sassu wrote:
> >> Thank you, I have tested that patch but the problem remained. Here is my
> >> command line, I wonder if there is something wrong.
> >>
> >> Kernel command line: rw rootfstype=initramtmpfs root=/dev/ram0
> >> initrd=0x500000000 rootwait
> >
> > It is just initramtmpfs, without rootfstype=.
> 
> Whoever wrote that patch really doesn't understand how this stuff works. I can
> tell from the name.

Hi Rob

surely, I should have been more careful in choosing the name of
the option.

> Technically, initramfs is the loader, I.E. "init ramfs". The filesystem instance
> is called "rootfs" (hence the name in /proc/mounts when the insane special case
> the kernel added doesn't hide information from people, making all this harder to
> understand for no obvious reason).

Ok, thanks for the explanation.

> ramfs and tmpfs are two different filesystems that COULD be used to implement
> rootfs. (Last I checked they were the only ram backed filesystems in Linux.)

Yes, that part I got it.

> If a system administrator says they're going to install your server's root
> partition using the "reiserxfs" filesystem, I would not be reassured.

Definitely.

[...]

> P.P.S. If you want to run a command other than /init out of initramfs or initrd,
> use the rdinit=/run/this option. Note the root= overmount mechanism is
> completely different code and uses the init=/run/this argument instead, which
> means nothing to initramfs. Again, specifying root= says we are NOT staying in
> initramfs.

Sorry, it was some time ago. I have to go back and see why we needed
a separate option. Maybe omitting root= was impacting on mounting
the real root filesystem. Will get that information.

Intuitively, given that root= is consumed for example by dracut, it seems
a safer choice to have an option to explicitly choose the desired filesystem.

Roberto

  parent reply	other threads:[~2022-07-19 12:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 12:18 [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-05-23 12:18 ` [PATCH v4 1/3] initramfs: add file metadata Roberto Sassu
     [not found]   ` <20190523121803.21638-2-roberto.sassu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2022-06-15 17:54     ` Eugeniu Rosca
2019-05-23 12:18 ` [PATCH v4 2/3] initramfs: read metadata from special file METADATA!!! Roberto Sassu
2019-07-01 12:54   ` Mimi Zohar
2019-05-23 12:18 ` [PATCH v4 3/3] gen_init_cpio: add support for file metadata Roberto Sassu
2019-06-30 15:27   ` Mimi Zohar
2022-06-16 14:47   ` Eugeniu Rosca
     [not found]   ` <20190523121803.21638-4-roberto.sassu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2022-06-16 15:16     ` Eugeniu Rosca
2022-06-30 15:06       ` Roberto Sassu
2022-06-30 20:38         ` Eugeniu Rosca
2019-06-03  9:31 ` [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-06-03 18:32   ` Rob Landley
2019-06-26  8:15     ` Roberto Sassu
2019-06-30 15:39       ` Mimi Zohar
2019-07-01 13:42         ` Roberto Sassu
2019-07-01 14:31           ` Mimi Zohar
2019-07-15 16:54             ` Roberto Sassu
2019-07-24 15:34               ` Roberto Sassu
2022-06-09 10:26                 ` Eugeniu Rosca
2022-06-09 11:05                   ` Roberto Sassu
2022-06-10 15:33                     ` Eugeniu Rosca
2022-06-10 15:38                       ` Roberto Sassu
2022-06-15  9:27                         ` Eugeniu Rosca
2022-07-18 16:36                           ` Jim Baxter
     [not found]                             ` <032ade35-6eb8-d698-ac44-aa45d46752dd-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2022-07-18 16:49                               ` Roberto Sassu
2022-07-18 18:08                                 ` Jim Baxter
2022-07-19  6:55                                   ` Roberto Sassu
     [not found]                                     ` <8e6a723874644449be99fcebb0905058-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2022-07-19 11:50                                       ` Rob Landley
     [not found]                                         ` <dc86769f-0ac6-d9f3-c003-54d3793ccfec-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2022-07-19 12:26                                           ` Roberto Sassu [this message]
2022-07-19 14:14                                             ` Rob Landley
2022-07-20 11:52                                               ` Roberto Sassu
2022-07-29 10:37                                     ` Jim Baxter
2022-07-30  9:39                                       ` Rob Landley
     [not found]                                   ` <737ddf72-05f4-a47e-c901-fec5b1dfa7a6-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2022-07-19 11:33                                     ` Rob Landley
2022-07-19 11:00                                 ` Rob Landley
2019-07-01 13:22 ` Mimi Zohar
2022-06-15 15:50 ` Alexander Lobakin
2022-06-15 16:03   ` Roberto Sassu
2022-06-16 13:24 ` Eugeniu Rosca

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=5b8b0bcac01b477eaa777ceb8c109f58@huawei.com \
    --to=roberto.sassu-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=Silviu.Vlasceanu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=bug-cpio-mXXj517/zsQ@public.gmane.org \
    --cc=dmitry.kasatkin-hv44wF8Li91hl2p70BpVqQ@public.gmane.org \
    --cc=erosca-Tbglbhd2jqSoSS7kgVBzIA@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jim_baxter-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-integrity-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=masahiroy-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=nivedita-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
    --cc=rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org \
    --cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
    --cc=zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=zohar-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org \
    /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