On Mon, 15 May 2000, Alexander Viro wrote: > > However, looks like you found a VFS bug that breaks ramfs - let's fix that > > one > > first.. > > I'm not that sure that VFS is at fault here - "you can't umount it, it's > not empty" sounds _very_ bogus. well, it sounded bogus intuitively but Linus did explain that it is a sensible policy for a ramfs filesystem. Are you saying that such policy cannot be implemented or that tha ramfs' trick of "extra" dget() is inadequate way of implementing it? Regards, Tigran
- VFS: Busy inodes after unmount... Petr Vandrovec
- Re: VFS: Busy inodes after unmount... Tigran Aivazian
- Re: VFS: Busy inodes after unmount... Alexander Viro
- Re: VFS: Busy inodes after unmount... Tigran Aivazian
- Re: VFS: Busy inodes after unmount... Alexander Viro
- Re: VFS: Busy inodes after unmou... Linus Torvalds
- Re: VFS: Busy inodes after u... Alexander Viro
- Re: VFS: Busy inodes aft... Linus Torvalds
- Re: VFS: Busy inodes aft... Jeremy Fitzhardinge
- Re: VFS: Busy inodes after unmount... Alexander Viro
- Re: VFS: Busy inodes after unmount... Petr Vandrovec