Messages in this thread | | | Date | Thu, 29 Oct 1998 19:26:00 -0500 (EST) | From | Alexander Viro <> | Subject | Re: nasty inode leak in 2.1.125? details |
| |
On Thu, 29 Oct 1998, Stephen C. Tweedie wrote:
> Hi, > > On Thu, 29 Oct 1998 10:18:23 +0000 (GMT), Chris Evans > <chris@ferret.lmh.ox.ac.uk> said: > > > Hi, > > > I just found out a way to make filesystems unmountable in 2.1.125, perhaps > > an inode or dentry leak. > > Have you managed to reproduce this? I've just tried exactly what you > describe, on 2.1.125, and it worked perfectly. Any process which is > cd'ed to that filesystem or has any open file there will block the > unmount.
Stephen, I also did hit it. In 2.1.126. Couldn't reproduce it yet. I've poked in /dev/kmem and it turned out that ->s_root->d_count was 2 without any obvious holders. So it sounds like dentry leak. And no, I don't know how I got there. _Not_ the way that Chris described, that's for sure.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |