Re: approach on getting nullfs to work again

看板DFBSD_kernel作者時間21年前 (2005/02/11 02:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串13/15 (看更多)
On Wed, Feb 09, 2005 at 09:38:15PM -0800, Matthew Dillon wrote: > In fact, *ALL* VOP or VFS ops that specify a file path have the same > ability to distinguish between namespaces as VOP ops that pass namecache > pointers, because path ops will also have access to the related namecache > pointer. Matt, shouldn't we fully separate vnode operation affection only the vnode (open, close, read, write) from those affection / depending on both the name space and the vnode? The first kind just has to be looked up and doesn't have to be handled by nullfs at all. For unionfs the situation would be a bit more complicated, but the underlying filesystem wouldn't have to be aware of unionfs for this operations. The second type is more difficult to handle, because the semantic of the operation (e.g. mknod or remove or mountctl) can be different for nullfs. This operations should be accessed by the mount point of the current name cache entry, not the vnode. It would not change the situation dramatically for normal filesystems, but allow stackable filesystems to just change what they need to change. Joerg
文章代碼(AID): #122w6I00 (DFBSD_kernel)
討論串 (同標題文章)
文章代碼(AID): #122w6I00 (DFBSD_kernel)