From: Willy Tarreau <w@1wt.eu>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][Patch] Allow not mounting a root fs
Date: Sat, 7 Jul 2007 23:46:48 +0200 [thread overview]
Message-ID: <20070707214648.GA28342@1wt.eu> (raw)
In-Reply-To: <Pine.LNX.4.58.0707072255260.3562@be1.lrz>
On Sat, Jul 07, 2007 at 11:18:59PM +0200, Bodo Eggert wrote:
> On Sat, 7 Jul 2007, Jan Engelhardt wrote:
> > On Jul 5 2007 19:08, H. Peter Anvin wrote:
>
> > >> BTW: Is it possible to mount a tmpfs on / before extracting the cpio?
> > >
> > >Not in the stock kernel. There have been some patches floating around
> > >for that, I think.
> >
> > What would it buy? rootfs is a tmpfs, is not it?
>
> As far as I understand, it is a ramfs aka. non-swappable tmpfs without any
> limit and including a chance of DoSing the system.
>
> Since I'm toying with root-on-initcpio, I'm looking for things that might
> make the task some easier.
>
> Currently I'm thinking about changing the root=initramfs to root=tmpfs and
> additionally mounting a tmpfs on / before unpacking the cpios. OTOH, this
> seems to be a little bit messy. OTOH again, in _that_ boot code, nobody
> should complain :)
Well, maybe it would be time to assign limits to ramfs. I have a patch for
this in all my own 2.4 kernels that I use on appliances, network boot and
bootable CDs. It was a bit tricky to get the limits to work well in 2.4
because it was not easy to track which pages were used by whom. But I presume
that rmap in 2.6 should help a lot.
If someone is willing to give this a try, here's the 2.4 patch :
http://linux.1wt.eu/kernel/patches-2.4.34-wt1/pool/2.4.32-ramfs-limits-5
Regards,
Willy
next prev parent reply other threads:[~2007-07-07 21:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 2:00 [RFC][Patch] Allow not mounting a root fs Bodo Eggert
2007-07-06 2:08 ` H. Peter Anvin
2007-07-06 15:00 ` Bodo Eggert
2007-07-06 15:32 ` Dan Aloni
2007-07-06 17:00 ` Andre Noll
2007-07-06 17:16 ` H. Peter Anvin
2007-07-07 18:30 ` Jan Engelhardt
2007-07-07 20:56 ` H. Peter Anvin
2007-07-07 21:13 ` Jan Engelhardt
2007-07-07 21:17 ` H. Peter Anvin
2007-07-18 21:51 ` Rob Landley
2007-07-18 22:50 ` H. Peter Anvin
2007-07-18 22:53 ` Roland M. Kruggel
2007-07-07 21:18 ` Bodo Eggert
2007-07-07 21:39 ` Jan Engelhardt
2007-07-07 21:45 ` H. Peter Anvin
2007-07-07 21:46 ` Willy Tarreau [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-08 10:36 Al Boldi
2007-07-11 0:46 ` H. Peter Anvin
2007-07-11 4:47 ` 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=20070707214648.GA28342@1wt.eu \
--to=w@1wt.eu \
--cc=7eggert@gmx.de \
--cc=hpa@zytor.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.