Changeset 204 for trunk/kernel/vfs/vfs.h

Timestamp:

Jul 17, 2017, 8:42:59 AM (6 years ago)

Author:

alain

Message:

Bug fix in kernel_init
-This line, and those below, will be ignored--

M params.mk
M kernel_config.h
M Makefile
M hdd/virt_hdd.dmg
M tools/bootloader_tsar/boot.c
M kernel/libk/bits.h
M kernel/libk/elf.c
M kernel/libk/xhtab.c
M kernel/libk/elf.h
M kernel/libk/xhtab.h
M kernel/devices/dev_pic.c
M kernel/mm/vmm.c
M kernel/mm/mapper.c
M kernel/mm/mapper.h
M kernel/vfs/devfs.h
M kernel/vfs/vfs.c
M kernel/vfs/vfs.h
M kernel/vfs/devfs.c
M kernel/kern/chdev.h
M kernel/kern/kernel_init.c
M kernel/kern/process.c
M kernel/kern/process.h
M hal/tsar_mips32/core/hal_remote.c
M hal/tsar_mips32/drivers/soclib_pic.c

File:

• trunk/kernel/vfs/vfs.h (modified) (3 diffs)

trunk/kernel/vfs/vfs.h

@@ -450 +450 @@
 
 /****************************************************************************************** 
+ * This debug function diplays the name of the inode identified by the <inode_xp>
+ * argument, and all children names for a directory.
+ *****************************************************************************************
+ * @ inode_xp  : extended pointer on the remote inode.
+ *****************************************************************************************/
+void vfs_inode_display( xptr_t inode_xp );
+
+
+
+
+
+
+/****************************************************************************************** 
  * This function TODO                                                          
  *****************************************************************************************/
@@ -617 +630 @@
  * It can be executed by any thread running in any cluster, as this function
  * uses the rpc_dentry_create_client() and rpc_inode_create client() if required.
- * - The dentry is created in the cluster containing the existing <parent_xp> inode.
- * - the inode and its associated mapper are created in cluster identified by <child_cxy>.
- * - The new dentry name is defined by the <name> argument.
- * - The new inode and the parent inode can have different FS types.
+ * This is done in three steps:
+ * 1) The dentry is created in the cluster containing the existing <parent_xp> inode.
+ *    The new dentry name is defined by the <name> argument.
+ * 2) The inode and its associated mapper are created in cluster identified by <child_cxy>.
+ *    The new inode and the parent inode can have different FS types.
+ * 3) The "child_xp" field in created dentry (pointing on thecreated inode) is updated.
  ******************************************************************************************
  * @ child_cxy  : target cluster for child inode.
@@ -629 +644 @@
  * @ extend     : fs_type_specific inode extension.
  * @ child_xp   : [out] buffer for extended pointer on child inode.
- * @ return 0 if success / ENOENT if entry not found in parent directory
+ * @ return 0 if success / ENOMEM if dentry or inode cannot be created.
  *****************************************************************************************/
 error_t vfs_add_child_in_parent( cxy_t              child_cxy,