From: Rob Landley <rob@landley.net>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Arvind Sankar <nivedita@alum.mit.edu>
Cc: initramfs <initramfs@vger.kernel.org>,
Taras Kondratiuk <takondra@cisco.com>,
Victor Kamensky <kamensky@cisco.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] rootfs: force mounting rootfs as tmpfs
Date: Thu, 1 Feb 2018 16:46:07 -0600 [thread overview]
Message-ID: <a9249307-9c95-ea75-bc83-7b95412e6ec4@landley.net> (raw)
In-Reply-To: <1517458921.3329.2.camel@linux.vnet.ibm.com>
On 01/31/2018 10:22 PM, Mimi Zohar wrote:
> On Wed, 2018-01-31 at 21:03 -0500, Arvind Sankar wrote:
>> On Wed, Jan 31, 2018 at 05:48:20PM -0600, Rob Landley wrote:
>>> On 01/31/2018 04:07 PM, Mimi Zohar wrote:
>>>> On Wed, 2018-01-31 at 13:32 -0600, Rob Landley wrote:>> (The old "I configured in tmpfs and am using rootfs but I want that
>>> rootfs
>>>>> to be ramfs, not tmpfs" code doesn't seem to be a real-world concern, does
>>>>> it?)
>>>>
>>>> I must be missing something. Which systems don't specify "root=" on
>>>> the boot command line.
>>>
>>> Any system using initrd or initramfs?
>>>
>>
>> Don't a lot of initramfs setups use root= to tell the initramfs which
>> actual root file system to switch to after early boot?
>
> With your patch and specifying "root=tmpfs", dracut is complaining:
>
> dracut: FATAL: Don't know how to handle 'root=tmpfs'
> dracut: refusing to continue
"The kernel can't break this buggy userspace package."
"The kernel must give access to a new feature to this buggy userspace
package".
I think kernel policy asks you to pick one, but I could be wrong...
Rob
prev parent reply other threads:[~2018-02-01 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 21:46 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
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 [this message]
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=a9249307-9c95-ea75-bc83-7b95412e6ec4@landley.net \
--to=rob@landley.net \
--cc=initramfs@vger.kernel.org \
--cc=kamensky@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nivedita@alum.mit.edu \
--cc=takondra@cisco.com \
--cc=viro@ZenIV.linux.org.uk \
--cc=zohar@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®