mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: cr@sap.com (Christoph Rohland)
Cc: torvalds@transmeta.com (Linus Torvalds),
	alan@lxorguk.ukuu.org.uk (Alan Cox),
	adam@yggdrasil.com (Adam J. Richter),
	parsley@roanoke.edu, linux-kernel@vger.kernel.org,
	riel@conectiva.com.br (Rik van Riel)
Subject: Re: Patch (repost): cramfs memory corruption fix
Date: Mon, 8 Jan 2001 14:42:18 +0000 (GMT)	[thread overview]
Message-ID: <E14FdV7-0004gd-00@the-village.bc.nu> (raw)
In-Reply-To: <qwwwvc6tbau.fsf@sap.com> from "Christoph Rohland" at Jan 08, 2001 02:37:13 PM

> 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 have been thinking about this. I think we should merge the size limiting code
with the example clean ramfs code. Having spent a while debugging the LFS
checks and some other funnies I realised one problem with the ramfs in
2.4.0 as an example. It does not demonstrate error cases, which the new one
does.


-
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/

  parent reply	other threads:[~2001-01-08 14:42 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
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 [this message]
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=E14FdV7-0004gd-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=adam@yggdrasil.com \
    --cc=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parsley@roanoke.edu \
    --cc=riel@conectiva.com.br \
    --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

all inboxes | Powered by JetHome®