[lkml]   [2001]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Patch (repost): cramfs memory corruption fix

On Sun, 7 Jan 2001, Alan Cox wrote:

> > > I'll take a look at the ramfs one. I may have broken something else when fixing
> > > everything else with ramfs (like unlink) crashing
> >
> > Ehh.. Plain 2.4.0 ramfs is fine, assuming you add a "UnlockPage()" to
> > ramfs_writepage(). So what do you mean by "fixing everything else"?
> -ac has the rather extended ramfs with resource limits and stuff. That one
> also has rather more extended bugs 8). AFAIK none of those are in the vanilla
> ramfs code

Ahh, ok.

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.

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.

Anyway, I'm quite sure that the resource stuff would not be 2.4.1 material
(adding the UnlockPage() is), so I won't have to worry about this issue
for a while.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.110 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site