On Dec 2, 2013, at 10:57, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > Trond, am I right interpreting you as "that filesystem has non-empty > contents only when there is at least one rpc_client in that netns; > after rpc_client removal there won't be any accesses to data structures > associated with it (due to rpc_close_pipes() and friends, presumably), > so there won't be any need to keep netns alive after that"? > > If so and if rpc_client really can't outlive netns, then yes, having each > of them hold an internal vfsmount reference pinning rpc_pipefs down would > suffice. We do have some “external” users but in practice their lifetimes are bounded by the lifetimes of the rpc_clients (See my reply to Christoph’s mail). So yes, I believe that it is the case that we need at least one rpc_client in a given nets for the filesystem to be non-empty. Cheers, Trond-- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
