summaryrefslogtreecommitdiffstats
path: root/cpukit/libfs (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Teach rtems_tarfs_load() about symlinksNick Withers2014-12-111-0/+17
|
* nfsclient: Avoid __FILE__ and __LINE__Sebastian Huber2014-12-051-3/+1
| | | | The __FILE__ prevents reproducible builds.
* nfs: Add RPCd task affinity config optionDaniel Cederman2014-12-022-0/+23
| | | | | | | | Similar to the task priority option, the new CPU affinity option is first controlled by the RPCI specific rpciodCpuset option. If that is not set, it uses the global network task config. If that is also not set, it falls back to not setting the affinity at all, using all CPUs.
* msdos_file.c: Reverse return codes per GedareJoel Sherrill2014-11-271-3/+3
|
* imfs/imfs_handlers_link.c: Add _Assert for NULL pointerJosh Oguin2014-11-261-0/+2
| | | | | CodeSonar flagged this as a possible dereference of a NULL pointer. This should never occur so adding _Assert().
* dosfs/msdos_misc.c: Remove unnecessary operationJosh Oguin2014-11-261-1/+1
| | | | | CodeSonar flagged the increment of this pointer as unneeded. The pointer is not used past this point.
* dosfs/msdos_file.c: Return an error if it occursJosh Oguin2014-11-261-1/+4
| | | | | CodeSonar flagged this as a case where the return value from fat_sync() was not used. Now it is used to return pass/fail to the caller.
* dosfs/msdos_conv.c: Remove unnecessary operationsJosh Oguin2014-11-261-3/+2
| | | | | | These were flagged by CodeSonar. The assignments on variable declaration are overridden a few lines below and the other line later with name_size is where name_size was not used after this assignment.
* rtems-rfs-rtems.c: Add cast to address warningJoel Sherrill2014-11-251-1/+1
|
* pipe/fifo.c: NULL dereference flagged by Coverity ID 1063889Joel Sherrill2014-11-211-1/+2
| | | | It does not appear that this is possible so adding an assert.
* dosfs/fat_fat_operations.c: Explicitly ignore return (Coverity ID 26048)Joel Sherrill2014-11-211-2/+7
| | | | | | Coverity spotted that the return code from fat_set_fat_cluster() was ignored. But it should be because we want to return the status that caused us to hit the cleanup path.
* dosfs/msdos_format.c: Dead code removal (Coverity ID 1255325)Joel Sherrill2014-11-211-75/+61
| | | | | Coverity identified that ret_val was never set except to be initialized to 0. Thus the code could not be executed.
* Delete or rename MIN/MAX macros and definesSebastian Huber2014-11-213-9/+3
| | | | Include <sys/param.h> if necessary to get the MIN()/MAX() macros.
* dosfs: Avoid MIN() re-definitionSebastian Huber2014-11-201-0/+2
|
* dosfs: Write meta-data only if it changedSebastian Huber2014-10-233-17/+40
|
* dosfs: Support ctime and mtimeSebastian Huber2014-10-239-133/+170
| | | | | | | Implement ctime and mtime updates according to POSIX. The ctime is mapped to the FAT create time and date. The mtime is mapped to the FAT last modified time and date. For the atime use the mtime for simplicity.
* cpukit/libfs/src/imfs/ioman.c: Fix typoJoel Sherrill2014-10-201-1/+1
|
* jffs2: Add casts and constant designators to address warnings on 16-bit targetsJoel Sherrill2014-10-193-3/+3
|
* jffs2/src/fs-rtems.c: Add include of <rtems/libio.h> for prototypesJoel Sherrill2014-10-161-0/+1
|
* jffs2/src/fs-rtems.c: Eliminate set but not used warningsJoel Sherrill2014-10-161-0/+3
|
* rfs: explicitly cast to dev_tGedare Bloom2014-10-161-1/+1
|
* Revert: rtems-rfs-buffer.c: Correct printf() format specifiers to eliminate ↵Joel Sherrill2014-09-161-2/+3
| | | | | | warnings This may actually be a problem in inttypes.h.
* dosfs: Check error statusSebastian Huber2014-09-111-14/+16
|
* rtems-rfs-buffer.c: Correct printf() format specifiers to eliminate warningsJoel Sherrill2014-09-041-3/+2
|
* libfs: Fix the warning in the RFS.Chris Johns2014-09-031-1/+6
| | | | Return the first error if one or more happen when deleting an inode.
* Regenerate all preinstall.am files.Chris Johns2014-08-291-6/+6
| | | | | With this patch the preinstall.am files are in a set order and not dependent on now perl implements a hash.
* JFFS2: Add device identifier for the flash deviceSebastian Huber2014-06-132-3/+15
| | | | | It is used in combination with the inode number to uniquely identify a file system node in the system.
* dosfs: Fix read from invalid memory areaSebastian Huber2014-05-161-1/+1
|
* libfs/rfs: Fix the fstime failures for the RFS file system.Chris Johns2014-04-252-12/+22
|
* Change all references of rtems.com to rtems.org.Chris Johns2014-03-21153-153/+153
|
* dosfs/fat.c: Remove use of register keywordJoel Sherrill2014-02-031-1/+1
|
* IMFS: Improved support for generic nodesSebastian Huber2014-01-212-3/+3
| | | | | | | | | | | | | | | | The rtems_filesystem_location_info_t::node_access_2 was unused by the IMFS. Use it to hold the context of generic nodes. This makes it possible to use node handlers for objects with and without a corresponding file system node. For example network sockets created with socket() have only a file descriptor, but no corresponding file system node. The UNIX(4) domain sockets can be bound to file system nodes. In both cases the rtems_filesystem_location_info_t must provide a pointer to the socket structure used by the socket node handlers. With the context pointer (for sockets, this is the socket structure) in rtems_filesystem_location_info_t::node_access_2 the same node handlers can be used in both cases.
* IMFS: Allow sockets as generic nodesSebastian Huber2014-01-211-1/+2
|
* libcsupport: Accept NULL for zero-length entriesSebastian Huber2013-12-202-20/+28
|
* Filesystem: Use default kqfilter and poll handlerSebastian Huber2013-12-2015-0/+38
|
* Filesystem: Add readv/writev handlersSebastian Huber2013-12-2018-89/+249
| | | | | | | | | The readv() and writev() support was implemented in terms of multiple calls to the read and write handlers. This imposes a problem on device files which use an IO vector as single request entity. For example a low-level network device (e.g. BPF(4)) may use an IO vector to create one frame from multiple protocol layers each with its own IO vector entry.
* For PR 2164 - RFS File System - fix bitmap_create_search loop bugAlan Cudmore2013-12-191-1/+2
| | | | | | | | | | | | | | | | | This is for the RFS file system. There is a bug in the rtems_rfs_bitmap_create_search loop. It is supposed to iterate over the range of bits in a search element ( usually 32 bits ), so it should loop through bits 0 through 31. Instead it loops through 0 - 32, causing some blocks not to be allocated. As in PR 2163, this depends on the block size and number of blocks in a file system. Block sizes and group sizes that are powers of 2 seem to work fine ( 512 byte blocks, 4096 block groups, etc ). When the block sizes are not powers of 2, then this loop error causes some of the blocks at the end of a group to be skipped, preventing 100% of the blocks from being used. A simple test for this and PR2163 is to create a RAM disk with block size 3900 and at least 1 full group ( 31200 blocks ). A file system with these sizes will not be able to allocate 100% of the blocks.
* For PR 2162 - RFS File System - statvfs reports 1 block freeAlan Cudmore2013-12-192-2/+2
| | | | | | | | | This is for the RFS file system. The statvfs call reports 1 block free when the file system is full because it does not account for the superblock in its calculation of free blocks. This is a simple fix that adjusts the number of blocks reported to account for the superblock. We may want to wait for a more complete solution such as locating the superblock in each group.
* For PR 2163 - RFS File System - fix group search algorithm bugAlan Cudmore2013-12-191-1/+15
| | | | | | | | | This is for the RFS file system. There is a bug in the group search algorithm where it will skip groups, causing blocks to remain unallocated. This is dependant on the size of the blocks and number of blocks in a group, so it does not always show up. The fix corrects the skipping of groups during the search, allowing all of the blocks to be found.
* nfsclient: Move defines to cover all header filesSebastian Huber2013-12-161-2/+3
|
* JFFS2: Do not re-define struct iovecSebastian Huber2013-12-161-5/+1
|
* PR2160: imfs: Use ENOSYS for unsupported nodesSebastian Huber2013-12-114-7/+18
| | | | | Return an error status with errno set to ENOSYS during node creation for nodes not available in the current configuration.
* PR2138: rtems_rfs_rtems_initialize() can erroneously set errno.Chris Johns2013-12-101-1/+1
| | | | Patch from Nick for this. Thanks.
* PR2159: Have the FIFO driver read follow POSIX standard.Chris Johns2013-12-101-43/+41
| | | | | The read call was only returning once the requested buffer was full. The change returns any available data.
* libfs/imfs: Set the FIFO control block.Chris Johns2013-12-101-1/+1
| | | | The FIFO was incorrectly set to the default control block.
* statvfs filesystem handlers: Remove restrictJoel Sherrill2013-11-274-12/+12
|
* statvfs and ALL filesystem handlers: Add restrict keyword.Daniel Ramirez2013-11-217-18/+21
|
* Filesystem: Add kernel event filter handlerSebastian Huber2013-11-042-0/+39
| | | | | | This handler is necessary to implement the KQUEUE(2) system calls. Add <sys/event.h> from FreeBSD 8.4.
* Filesystem: Add poll() handlerSebastian Huber2013-11-042-0/+38
| | | | | | | This handler is necessary to implement the SELECT(2) and POLL(2) system calls. Add <sys/poll.h> from FreeBSD 8.4.
* Filesystem: Use ENOTTY for default ioctl() handlerSebastian Huber2013-10-311-1/+1
| | | | This is in line with Linux and FreeBSD.