> OK, explain me, in small words, WTF should something that wants to do > operations on filesystem tree have a vfsmount. Slowly. And BTW in the highly unlikely case, that something didn't have a vfsmount and wanted to do some operation, it _should_ definitely just allocate a kernel-private mount for that. Why? Because that means that another interface, namely the grab-sb-for-write and release-sb-for-write interfaces won't have to be exported for such users, resulting in an overall smaller and simpler API. And that's good. Now tell me in small words, why do we need the vfs_ interface to stay around? Miklos -- 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
