From: Christoph Hellwig <hch@caldera.de>
To: cr@sap.com (Christoph Rohland)
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Patch (repost): cramfs memory corruption fix
Date: Mon, 8 Jan 2001 15:19:25 +0100 [thread overview]
Message-ID: <200101081419.PAA26150@ns.caldera.de> (raw)
In-Reply-To: <qwwwvc6tbau.fsf@sap.com>
In article <qwwwvc6tbau.fsf@sap.com> you wrote:
> Hi Linus,
>
> On Sun, 7 Jan 2001, Linus Torvalds wrote:
>> 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.
>
> Let me repeat on this issue: shmem.c has everything needed for this
> despite read and write and they should be really easy to add.
>
> I did not plan to write them in the near future because I did not
> think that this is a really wanted feature. But I can look into it.
>
I had a prototype tmpfs in -test10 (ro so) times. It based on ramfs
for all the metadata stuff and used the (old) shmfs code for swap-backed
data. The only real problem the code had, was that it needed a ->allocpage
address_space method in place of page_cache_alloc() to directly swap-in
pages in ->read. IF anyone is interested I could forward port it to 2.4.0
and the new shmfs.
Christoph
--
Whip me. Beat me. Make me maintain AIX.
-
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-08 14:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 6:41 Patch (repost): cramfs memory corruption fix 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
2001-01-08 13:37 ` Christoph Rohland
2001-01-08 14:19 ` Christoph Hellwig [this message]
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=200101081419.PAA26150@ns.caldera.de \
--to=hch@caldera.de \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--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