public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Al Boldi <a1426z@gawab.com>
Cc: Rob Landley <rob@landley.net>,
	linux-kernel@vger.kernel.org, torvalds@osdl.org,
	stable@kernel.org, akpm@osdl.org, chrisw@sous-sol.org,
	grim@undead.cc, Hugh Dickins <hugh@veritas.com>
Subject: Re: [PATCH] initramfs:  Allow rootfs to use tmpfs instead of ramfs
Date: Mon, 31 Jul 2006 12:24:30 -0700	[thread overview]
Message-ID: <44CE58EE.1090409@zytor.com> (raw)
In-Reply-To: <200607310003.48637.a1426z@gawab.com>

Al Boldi wrote:
>>
>> The main issue -- which I am not sure what effect this patch has -- is
>> that we would really like to move initramfs initialization even earlier
>> in the kernel, so that it can include firmware loading for built-in
>> device drivers, for example.
> 
> I suspect, if there would be a problem with tmpfs, then ramfs would be no 
> different.
> 

That is a very bold assumption (a.k.a. "just plain wrong".)  ramfs and 
tmpfs are a lot more different than one would normally think from a 
kernel internals perspective.

>> Thus, if this patch makes it harder to push initramfs initialization
>> earlier, it's probably a bad thing.
> 
> Agreed, but remember that tmpfs is an option, not a replacement.

Red herring.  If it goes in, it needs to be supportable going forward.

>> If not, the author of the patch
>> really needs to explain why it works and why it doesn't add new
>> dependencies to the initialization order.
>>
>> Saying "this is a trivial patch" and pushing it on the -stable tree
>> doesn't inspire too much confidence, as initialization is subtle.
> 
> Ok, I did play with main.c, and as you mentioned, initialization is subtle.  
> But categorizing this patch as trivial is based more on the fact, that ramfs 
> and tmpfs are semantically equivalent, and as such should not impose 
> additional dependencies.

Again, that's just plain wrong.

	-hpa

  reply	other threads:[~2006-07-31 19:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 15:08 [PATCH] initramfs: Allow rootfs to use tmpfs instead of ramfs Al Boldi
2006-07-30 17:36 ` Hugh Dickins
2006-07-30 18:48   ` H. Peter Anvin
2006-07-30 21:03     ` Al Boldi
2006-07-31 19:24       ` H. Peter Anvin [this message]
2006-07-31 14:35     ` Rob Landley
2006-07-30 21:03   ` Al Boldi
2006-07-30 17:51 ` [stable] " Greg KH
2006-07-30 21:03   ` Al Boldi
2006-07-31 19:25     ` H. Peter Anvin
2006-07-31 20:58       ` Al Boldi
2006-07-31 23:20         ` H. Peter Anvin
2006-07-31 19:30     ` Chris Wright
2006-07-31 20:58       ` Al Boldi

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=44CE58EE.1090409@zytor.com \
    --to=hpa@zytor.com \
    --cc=a1426z@gawab.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=grim@undead.cc \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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