Received: by 10.223.176.5 with SMTP id f5csp2148502wra; Wed, 31 Jan 2018 18:04:18 -0800 (PST) X-Google-Smtp-Source: AH8x224ibMB5Bu+7DOH5wlo3X2P3JNc1ANzaT+cn5dkJGzry6Pmwod5zec2iTG1MgnvEls6Stei3 X-Received: by 2002:a17:902:2943:: with SMTP id g61-v6mr28808146plb.435.1517450658148; Wed, 31 Jan 2018 18:04:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517450658; cv=none; d=google.com; s=arc-20160816; b=lf3bfDaa36TEwDeEKCOUxs5V8Yz/8UnKY6gBiW9gU0+RT/YAKMZp2n8DrgFcOQoRuf luhMzHozBcUyZolXJeY5he/WUUAQRiNdtDIVVX5mhK9qFuZVrUinIYl9zkcTTETjTCjI 9MRzP5tfGHpZsRt/ZUmgSX5DYUU1CH7MKfdyOpfdiQNfVwmQCEeC5Qst5x0PujuOKjyu aOA7SrVO5u7U/is/rOxlPwI7E2aXAhEOI0vwT9LsXssdSfXsiHlTwnGbV/uauRtJEMny hXUSkmizpZsFTJvY8mABDhbYRk9j08lXfAu+wRbtm+kHBLdJJc1FnMdIcBsvRBh5+jng woAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=wElTZ3Qecp7FusJ21drD6USlYu2J6lseNfyVe40jDKk=; b=q99FwYVX7Xbeq7eNJ7Pc1z7Atzd7oRpZHYwoutVEPzXgcYaHnjeTC1P/qhnEu7ujlv MFPLHpR1uGlBxmL9N3Ky5PG0KJbhUT4tMKvSFocQlqwhcejEAF7j706CQjhv2bqD9l2i UsQnzQTbQb/0df0SWwlfjmxHkt2EVxAORcrl8+O0PyZMB/j9MompfRYjMxVk61xG+FJM yzba0aLQtbPYLw8ye0wKuhnpI+3Wli6fAuo3c0qh4IwgVwRYBA85kse/0cpUCt2sYvkn iMKOqMIVszCUYA7ySUv4dgSmYoCualeY+QX2sLEmgzBWGZMqmADbY5UCIjrcrUMnuTui N6Ow== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l24si12021969pgo.128.2018.01.31.18.04.02; Wed, 31 Jan 2018 18:04:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932207AbeBACDj (ORCPT + 99 others); Wed, 31 Jan 2018 21:03:39 -0500 Received: from mail-qt0-f195.google.com ([209.85.216.195]:40762 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932137AbeBACDh (ORCPT ); Wed, 31 Jan 2018 21:03:37 -0500 Received: by mail-qt0-f195.google.com with SMTP id s39so24502801qth.7; Wed, 31 Jan 2018 18:03:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=wElTZ3Qecp7FusJ21drD6USlYu2J6lseNfyVe40jDKk=; b=kstwLvqn6AzFHVK+mC0UK2MWYLtD5n6uZBU+6fbOqkWbFUtYneVLh3CLTBcrjkQ4YV z/fK27OINTVEiscwwaezVtA/OzcYPZ14hiYmOIbI2EX1MIKU9YPpIpSNPLp9GGxIHuVE aADaJOQfi9AK8i5F8KWLG7HaceHCbCIZvA5y8Kn6QaIlQboHRK6tyLZdxmLrBi/fXOS3 XkfKXb2boFrZpKnwFd2CqiHhOtVFlABL8aNVdwQcI7edahYRIIEb/ClBnEkZhQjS8jvE 4ceKEkW4LY+pl5mwptdBUQdfQMax48UfVEjuVdPZ7BZRKPyASiMUqx1doSlY5jfgazz2 SO9w== X-Gm-Message-State: AKwxytcFZTVWelTQG/ILZ/r7UKmBXulQB9Kgq1ryRTpSLTnqeTwb9L+U +is8Wl4nDENThckygVmO8kM= X-Received: by 10.200.28.145 with SMTP id f17mr29061321qtl.15.1517450616769; Wed, 31 Jan 2018 18:03:36 -0800 (PST) Received: from rani.riverdale (pool-100-8-221-136.nwrknj.fios.verizon.net. [100.8.221.136]) by smtp.gmail.com with ESMTPSA id y123sm11879186qka.42.2018.01.31.18.03.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 18:03:36 -0800 (PST) Date: Wed, 31 Jan 2018 21:03:32 -0500 From: Arvind Sankar To: Rob Landley Cc: Mimi Zohar , initramfs , Taras Kondratiuk , Victor Kamensky , linux-security-module , Al Viro , linux-kernel Subject: Re: [RFC PATCH] rootfs: force mounting rootfs as tmpfs Message-ID: <20180201020331.GA3774@rani.riverdale> References: <1517348777.3469.5.camel@linux.vnet.ibm.com> <1814af5c-170d-39c0-58fd-02eb7216e008@landley.net> <1517436423.3469.237.camel@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?