![]() | |||||||||||||
Messages in this thread |
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? Tim - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:02 [from the cache] ©2003-2008 | |||||||||||||