On Fri, 2 Feb 2001, Ingo Oeser wrote: > On Fri, Feb 02, 2001 at 08:24:19PM +0100, Mike Galbraith wrote: > > On Fri, 2 Feb 2001, Ingo Oeser wrote: > > > No, so have to unlock it also, if you return -ENOSPC. > > > > > > So the correct fix seems to be: > [...] > > > This currently works for me (but using 2.4.0 + dwg-ramfs.patch + this patch) > > > > Have you stressed it? (I see leakiness) > > I do reads and writes to it every 5 seconds and sometimes more ( > mounted on /tmp, /var/run and the like ) and had an uptime of > about a week (I use it in an embedded-like system and we > sometimes change the system image). > > There might be a dentry or inode leak, but that doesn't bite me, > because I only create the files I need once and extend or shrink > them. That won't show it. I can do that kind of stuff all day long, no problem whatsoever. > But I couldn't stress it too much. > > Where exactly do you see the leaks? (I don't have a solid grip yet.. just starting to seek) > PS: For reference, I put the diff to 2.4.0 that I use to > http://www.tu-chemnitz.de/~ioe/dwg-ramfs.patch > > The original patch has _not_ been done by me, but by > David Gibson, Linuxcare Australia. I'll take a look at this.. thanks. - 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/
