summaryrefslogtreecommitdiffstats
path: root/cpukit/libcsupport/src/sup_fs_location.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2017-03-21libio: Fix deadlock in location managementSebastian Huber1-4/+5
Perform a context-dependent deferred location release to avoid a deadlock on the file system instance locks, for example during a chdir(). Close #2936.
2015-05-19Filesystem: Use lock for deferred releaseSebastian Huber1-4/+17
2014-03-21Change all references of rtems.com to rtems.org.Chris Johns1-1/+1
2014-03-14score: Add SMP lock profiling supportSebastian Huber1-1/+1
2013-08-14filesystem: Add SMP supportSebastian Huber1-0/+3
2013-07-26Include missing <rtems/score/threaddispatch.h>Sebastian Huber1-3/+1
2013-06-14score: Add and use _Thread_Dispatch_is_enabled()Sebastian Huber1-1/+1
Delete _Thread_Dispatch_in_critical_section() and _Thread_Is_dispatching_enabled().
2012-12-15libcsupport: Doxygen Enhancement Task #8Alex Ivanov1-0/+7
http://www.google-melange.com/gci/task/view/google/gci2012/7996208
2012-10-30Filesystem: Use transient eventSebastian Huber1-1/+1
2012-05-29Filesystem: Wait for unmount() to finishSebastian Huber1-0/+9
2012-05-15Filesystem: Move operations to mount table entrySebastian Huber1-2/+1
The scope of the file system operations is the file system instance. The scope of the file system node handlers is the file location. The benefit of moving the operations to the mount table entry is a size reduction of the file location (rtems_filesystem_location_info_t). The code size is slightly increased due to additional load instructions. Restructure rtems_filesystem_mount_table_entry_t to improve cache efficiency.
2012-03-13Filesystem: Reference counting for locationsSebastian Huber1-0/+218
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.