From a37c845e5236137d5e5f46eafaea353b865594ea Mon Sep 17 00:00:00 2001 From: Ingo Weinhold Date: Thu, 4 Apr 2013 12:00:08 +0200 Subject: [PATCH] FS interface API doc: More details for unmount() --- docs/user/drivers/fs_interface.dox | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/user/drivers/fs_interface.dox b/docs/user/drivers/fs_interface.dox index ec891e1afa..edfe0573fe 100644 --- a/docs/user/drivers/fs_interface.dox +++ b/docs/user/drivers/fs_interface.dox @@ -325,8 +325,11 @@ Invoked by the VFS when it is asked to unmount the volume. The function must free all resources associated with the mounted volume, including the volume - handle. Although the mount() hook called publish_vnode() for the root node - of the volume, unmount() must not invoke put_vnode(). + handle. Before unmount() is called, the VFS calls + file_system_module_info::put_vnode() respectively + file_system_module_info::remove_vnode() for each of the volume's nodes. That + is although the mount() hook called publish_vnode() for the volume's root + node, unmount() must not invoke put_vnode(). \param volume The volume object. \return \c B_OK if everything went fine, another error code otherwise. The