> > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Patch (repost): cramfs memory corruption fix Adam J. Richter
- Re: Patch (repost): cramfs memory corruption fix Alan Cox
- Re: Patch (repost): cramfs memory corruption fi... Linus Torvalds
- Re: Patch (repost): cramfs memory corruptio... Alan Cox
- Re: Patch (repost): cramfs memory corru... Linus Torvalds
- Re: Patch (repost): cramfs memory ... Rik van Riel
- Re: Patch (repost): cramfs mem... Alan Cox
- Re: Patch (repost): cramfs mem... Eric W. Biederman
- Re: Patch (repost): cramfs memory ... Christoph Rohland
- Re: Patch (repost): cramfs mem... Christoph Hellwig
- Re: Patch (repost): cramfs... Christoph Rohland
- Re: Patch (repost): cramfs mem... Alan Cox
- Re: Patch (repost): cramfs... Christoph Rohland
- Re: Patch (repost): cramfs memory corru... David L. Parsley