Filesystem: Reference counting for locations

 o A new data structure rtems_filesystem_global_location_t was
   introduced to be used for
    o the mount point location in the mount table entry,
    o the file system root location in the mount table entry,
    o the root directory location in the user environment, and
    o the current directory location in the user environment.
   During the path evaluation global start locations are obtained to
   ensure that the current file system instance will be not unmounted in
   the meantime.
 o The user environment uses now reference counting and is protected
   from concurrent access.
 o The path evaluation process was completely rewritten and simplified.
   The IMFS, RFS, NFS, and DOSFS use now a generic path evaluation
   method.  Recursive calls in the path evaluation have been replaced
   with iteration to avoid stack overflows.  Only the evaluation of
   symbolic links is recursive.  No dynamic memory allocations and
   intermediate buffers are used in the high level path evaluation.  No
   global locks are held during the file system instance specific path
   evaluation process.
 o Recursive symbolic link evaluation is now limited by
   RTEMS_FILESYSTEM_SYMLOOP_MAX.  Applications can retrieve this value
   via sysconf().
 o The device file system (devFS) uses now no global variables and
   allocation from the workspace.  Node names are allocated from the
   heap.
 o The upper layer lseek() performs now some parameter checks.
 o The upper layer ftruncate() performs now some parameter checks.
 o unmask() is now restricted to the RWX flags and protected from
   concurrent access.
 o The fchmod_h and rmnod_h file system node handlers are now a file
   system operation.
 o The unlink_h operation has been removed.  All nodes are now destroyed
   with the rmnod_h operation.
 o New lock_h, unlock_h, clonenod_h, and are_nodes_equal_h file system
   operations.
 o The path evaluation and file system operations are now protected by
   per file system instance lock and unlock operations.
 o Fix and test file descriptor duplicate in fcntl().
 o New test fstests/fsnofs01.

1 files changed, 0 insertions, 151 deletions

diff --git a/cpukit/libcsupport/src/eval.c b/cpukit/libcsupport/src/eval.c
deleted file mode 100644
index 5a9118d3e1..0000000000
--- a/cpukit/libcsupport/src/eval.c
+++ /dev/null
@@ -1,151 +0,0 @@
-/*
- *  rtems_filesystem_evaluate_path()
- *
- *  Routine to seed the evaluate path routine.
- *
- *  COPYRIGHT (c) 1989-2010.
- *  On-Line Applications Research Corporation (OAR).
- *
- *  The license and distribution terms for this file may be
- *  found in the file LICENSE in this distribution or at
- *  http://www.rtems.com/license/LICENSE.
- *
- *  $Id$
- */
-
-#if HAVE_CONFIG_H
-#include "config.h"
-#endif
-
-#include <rtems.h>
-#include <rtems/libio_.h>
-#include <rtems/seterr.h>
-
-int rtems_filesystem_evaluate_relative_path(
-  const char                        *pathname,
-  size_t                             pathnamelen,
-  int                                flags,
-  rtems_filesystem_location_info_t  *pathloc,
-  int                                follow_link
-)
-{
-  int                           result;
-  rtems_filesystem_node_types_t type;
-
-  #if defined(RTEMS_DEBUG)
-    /*
-     * Verify Input parameters that should never be bad unless someone
-     * is implementing a new filesystem and has bugs.
-     */
-    if ( !pathname )
-      rtems_set_errno_and_return_minus_one( EFAULT );
-
-    if ( !pathloc )
-      rtems_set_errno_and_return_minus_one( EIO );
-  #endif
-
-  result = (*pathloc->ops->evalpath_h)( pathname, pathnamelen, flags, pathloc );
-
-  /*
-   * Get the Node type and determine if you need to follow the link or
-   * not.
-   */
-
-  if ( (result == 0) && follow_link ) {
-
-    type = (*pathloc->ops->node_type_h)( pathloc );
-
-    if ( ( type == RTEMS_FILESYSTEM_HARD_LINK ) ||
-         ( type == RTEMS_FILESYSTEM_SYM_LINK ) ) {
-
-        /* what to do with the valid node pathloc points to
-         * if eval_link_h fails?
-         * Let the FS implementation deal with this case.  It
-         * should probably free pathloc in either case:
-         *  - if the link evaluation fails, it must free the
-         *    original (valid) pathloc because we are going
-         *    to return -1 and hence the FS generics won't
-         *    cleanup pathloc.
-         *  - if the link evaluation is successful, the updated
-         *    pathloc will be passed up (and eventually released).
-         *    Hence, the (valid) originial node that we submit to
-         *    eval_link_h() should be released by the handler.
-         */
-
-        result =  (*pathloc->ops->eval_link_h)( pathloc, flags );
-    }
-  }
-
-  return result;
-}
-
-int rtems_filesystem_evaluate_path(
-  const char                        *pathname,
-  size_t                             pathnamelen,
-  int                                flags,
-  rtems_filesystem_location_info_t  *pathloc,
-  int                                follow_link
-)
-{
-  int                           i = 0;
-
-  #if defined(RTEMS_DEBUG)
-    /*
-     * Verify Input parameters that should never be bad unless someone
-     * is implementing a new filesystem and has bugs.
-     */
-    if ( !pathname )
-      rtems_set_errno_and_return_minus_one( EFAULT );
-
-    if ( !pathloc )
-      rtems_set_errno_and_return_minus_one( EIO );
-  #endif
-
-  /*
-   * Evaluate the path using the optable evalpath.
-   */
-
-  rtems_filesystem_get_start_loc( pathname, &i, pathloc );
-
-  /*
-   * We evaluation the path relative to the start location we get got.
-   */
-  return rtems_filesystem_evaluate_relative_path( &pathname[i],
-                                                  pathnamelen - i,
-                                                  flags,
-                                                  pathloc,
-                                                  follow_link );
-}
-
-int rtems_filesystem_dirname(
-  const char  *pathname
-)
-{
-  int len = strlen( pathname );
-
-  while ( len ) {
-    len--;
-    if ( rtems_filesystem_is_separator( pathname[len] ) )
-      break;
-  }
-
-  return len;
-}
-
-int rtems_filesystem_prefix_separators(
-  const char  *pathname,
-  int          pathnamelen
-)
-{
-  /*
-   * Eat any separators at start of the path.
-   */
-  int stripped = 0;
-  while ( *pathname && pathnamelen && rtems_filesystem_is_separator( *pathname ) )
-  {
-    pathname++;
-    pathnamelen--;
-    stripped++;
-  }
-  return stripped;
-}