Re: lazy-umount cwd and ..

[viro]

On Wed, May 05, 2004 at 09:44:33PM -0700, Tim Hockin wrote:
> I notice that a process that is in a dir which gets lazy-unmounted
> suddenly sees it's current dir change and its '..' dir points back to
> itself.
> 
> I'm not sure it's a huge deal, but we have a half-patch floating around
> that changes the behavior such that the unmounted mnt->mnt_parent is
> retained and unreferenced when the mnt is finally released.  This seems to
> make any process which is in the unmounted mount not see anything
> different, but does not let any new processes into the mount.
> 
> Minor, but friendly.
> 
> Should I bother to polish this patch off and send it, or is it just not
> something we want to care about?

No.  This is simply wrong - one of the situations when you want lazy-umount
is getting a stuck filesystem (e.g. NFS mounted hard) and wanting to get
it out of the way, so that stuff it's mounted on could be unmounted clean.

So we definitely don't want to keep anything pinned down.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/