From: Chris Wedgwood <cw@f00f.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Adam J. Richter" <adam@yggdrasil.com>,
parsley@roanoke.edu, linux-kernel@vger.kernel.org
Subject: Re: Patch (repost): cramfs memory corruption fix
Date: Mon, 8 Jan 2001 10:54:09 +1300 [thread overview]
Message-ID: <20010108105409.B3904@metastasis.f00f.org> (raw)
In-Reply-To: <E14FLi2-0003Cy-00@the-village.bc.nu> <Pine.LNX.4.10.10101071153470.27944-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10101071153470.27944-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Sun, Jan 07, 2001 at 11:56:38AM -0800
On Sun, Jan 07, 2001 at 11:56:38AM -0800, Linus Torvalds wrote:
This is actually where I agree with whoever it was that said that
ramfs as it stands now (without the limit checking etc) is much
nicer simply because it can act as an example of how to do a
simple filesystem.
That was me. ramfs is mimnimalist and if we must extend/bloat ramfs
then I suggest we adding a backing store al la tmpfs or memfs and
change it's name.
Don't get me wrong, I _like_ ramfs and want a backing store and
perhaps limits (I use ramfs for /tmp and decided to put over a
million files in there once as a test, kaboom), but I'm no guru and
would love to see ramfs stay as is -- because _I_ can understand it.
To me, that is worth a lot -- ramfs is only 8k, tiny to keep about as
an example I should think.
I wonder what to do about this - the limits are obviously useful,
as would the "use swap-space as a backing store" thing be. At the
same time I'd really hate to lose the lean-mean-clean ramfs.
ramfs-> skeletonfs
ramfs+bloat -> vmfs
--cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-07 21:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 6:41 Adam J. Richter
2001-01-07 13:53 ` Alan Cox
2001-01-07 19:26 ` Linus Torvalds
2001-01-07 19:42 ` Alan Cox
2001-01-07 19:56 ` Linus Torvalds
2001-01-07 21:11 ` Rik van Riel
2001-01-07 21:20 ` Alan Cox
2001-01-08 6:56 ` Eric W. Biederman
2001-01-07 21:54 ` Chris Wedgwood [this message]
2001-01-08 13:37 ` Christoph Rohland
2001-01-08 14:19 ` Christoph Hellwig
2001-01-08 14:43 ` Christoph Rohland
2001-01-08 14:42 ` Alan Cox
2001-01-08 14:49 ` Christoph Rohland
2001-01-07 20:39 ` David L. Parsley
2001-01-08 18:27 ` Linus Torvalds
2001-01-08 3:46 ` Linus Torvalds
2001-01-08 13:11 ` David Woodhouse
2001-01-08 12:30 ` Shane Nay
2001-01-08 14:34 ` David Woodhouse
2001-01-10 23:30 ` [PATCH] one-liner fix for bforget() honoring BH_Protected; was: " David L. Parsley
2001-01-11 4:23 ` Linus Torvalds
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=20010108105409.B3904@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=adam@yggdrasil.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=parsley@roanoke.edu \
--cc=torvalds@transmeta.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
Powered by JetHome