Subject: Re: INITRAMFS_SOURCE broken by
 6e19eded3684dc184181093af3bff2ff440f5b53?
To: Willy Tarreau <w@1wt.eu>, Thomas Meyer <thomas@m3y3r.de>
Cc: linux-kernel@vger.kernel.org
References: <20170808114625.GA13532@localhost.localdomain>
 <20170808120442.GE27367@1wt.eu>
From: Rob Landley <rob@landley.net>
Message-ID: <6a32fa08-d11a-e49e-89f2-a874978c8d79@landley.net>
Date: Tue, 8 Aug 2017 17:12:03 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170808120442.GE27367@1wt.eu>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 973
Lines: 26

On 08/08/2017 07:04 AM, Willy Tarreau wrote:
> Hi Thomas,
> 
> On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote:
>> Hi,
>>
>> did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel
>> build with an included ramdisk?
>>
>> As fas as I understand you must expliclity add rootfstype=ramfs to the kernel
>> command line to boot from the included ramfsdisk?
>>
>> bug or feature?
> 
> Strange, I'm running my kernels with the modules packaged inside the initramfs
> and never met this problem even after this commit (my 4.9 kernels are still
> packaged this way and run fine). And yes, I do have TMPFS enabled. I can't
> tell whether tmpfs or ramfs was used however given that at this level I don't
> have all the tools available to report the FS type (and proc says "rootfs").
> Are you sure you're not missing anything ?

If your rootfs has a size= in /proc/mounts it's tmpfs, ala:

  rootfs / rootfs rw,size=126564k,nr_inodes=31641 0 0

Rob