Files
rtems/testsuites
Sebastian Huber 3b7c123c8d 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.
2012-03-13 12:23:37 +01:00
..
2012-02-01 10:59:44 -06:00
2012-02-01 10:59:44 -06:00
2012-02-01 10:59:44 -06:00
2012-02-01 10:59:44 -06:00

#
#  $Id$
#

This is the directory under which the RTEMS
test programs provided with the release are located.  The
following is a description of the contents of each file and
subdirectory directly in this directory:

NOTE: Other than the 'samples' directory these tests are intended
      only to exercise RTEMS features and are *not* good examples
      of programming for RTEMS.

    samples

       This directory contains a set of simple sample applications
       which can be used either to test a board support package
       or as the starting point for a custom application.

    mptests

       This directory contains the RTEMS Multiprocessor Test Suite.
       The tests in this directory provide near complete (98%+) test
       coverage of the multiprocessor specific code in RTEMS.

    psxtests

       This directory contains the RTEMS POSIX API Test Suite.
       The tests in this directory test the POSIX API support in RTEMS.

    sptests

       This directory contains the RTEMS Single Processor Test Suite.
       The tests in this directory provide near complete (98%+) test
       coverage of the non-multiprocessor code in RTEMS.

    tmtests

       This directory contains the RTEMS Timing Test Suite.
       The tests in this directory are used to measure the execution
       time of RTEMS directive and some critical internal functions.
       The results of these test are reported in the Fact Sheets
       and Supplental Manuals.