linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH] rootfs: force mounting rootfs as tmpfs
Date: Thu, 01 Feb 2018 16:51:52 -0500	[thread overview]
Message-ID: <1517521912.3619.0.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <875e5d2d-9ffe-14ab-090a-4a9632af0f35@landley.net>

On Thu, 2018-02-01 at 11:09 -0600, Rob Landley wrote:
> On 02/01/2018 09:55 AM, Mimi Zohar wrote:
> > On Thu, 2018-02-01 at 09:20 -0600, Rob Landley wrote:
> > 
> >>> With your patch and specifying "root=tmpfs", dracut is complaining:
> >>>
> >>> dracut: FATAL: Don't know how to handle 'root=tmpfs'
> >>> dracut: refusing to continue
> >>
> >> [googles]... I do not understand why this package exists.
> >>
> >> If you're switching to another root filesystem, using a tool that
> >> wikipedia[citation needed] says has no purpose but to switch to another
> >> root filesystem, (so let's reproduce the kernel infrastructure in
> >> userspace while leaving it the kernel too)... why do you need initramfs
> >> to be tmpfs? You're using it for half a second, then discarding it,
> >> what's the point of it being tmpfs?
> > 
> > Unlike the kernel image which is signed by the distros, the initramfs
> > doesn't come signed, because it is built on the target system. ?Even
> > if the initramfs did come signed, it is beneficial to measure and
> > appraise the individual files in the initramfs.
> 
> You can still shoot yourself in the foot with tmpfs. People mount a /run
> and a /tmp and then as a normal user you can go
> https://twitter.com/landley/status/959103235305951233 and maybe the
> default should be a little more clever there...
> 
> I'll throw it on the todo heap. :)
> 
> >> Sigh. If people are ok with having rootfs just be tmpfs whenever tmpfs
> >> is configured in, even when you're then going to overmount it with
> >> something else like you're doing, let's just _remove_ the test. If it
> >> can be tmpfs, have it be tmpfs.
> > 
> > Very much appreciated!
> 
> Not yet tested, but something like the attached? (Sorry for the
> half-finished doc changes in there, I'm at work and have a 5 minute
> break. I can test properly this evening if you don't get to it...)

Yes, rootfs is being mounted as tmpfs.

Mimi

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-02-01 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 21:46 [RFC PATCH] rootfs: force mounting rootfs as tmpfs Mimi Zohar
2018-01-31 19:32 ` Rob Landley
2018-01-31 22:07   ` Mimi Zohar
2018-01-31 23:48     ` Rob Landley
2018-02-01  2:03       ` Arvind Sankar
2018-02-01  4:22         ` Mimi Zohar
2018-02-01 15:20           ` Rob Landley
2018-02-01 15:55             ` Mimi Zohar
2018-02-01 17:09               ` Rob Landley
2018-02-01 21:51                 ` Mimi Zohar [this message]
2018-02-01 22:41                   ` Taras Kondratiuk
2018-02-01 23:34                     ` Rob Landley
2018-04-16 15:46                       ` Mimi Zohar
2018-02-01 22:46           ` Rob Landley

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=1517521912.3619.0.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=linux-security-module@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).