| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Update #3132.
|
|
|
|
|
|
| |
Do not update the non-existant meta-data of the root directory.
Update #2944.
|
|
|
|
| |
Update #2964.
|
|
|
|
|
|
| |
Set a proper name buffer length for each converter invocation.
Update #2987.
|
|
|
|
| |
Close #3003.
|
|
|
|
| |
Update #2133.
|
|
|
|
|
|
|
|
|
|
|
| |
Added a mmap file handler to struct _rtems_filesystem_file_handlers_r.
Updated each file handler object to support the default mmap handler.
Updated mmap() to call the mmap handler for MAP_SHARED.
Added a mmap file handler for shm
Added support for MAP_ANON in mmap().
Updates #2859
|
|
|
|
|
|
| |
Some kernel-space header expect that <sys/param.h> is present.
Update #2833.
|
|
|
|
| |
Update #2833.
|
| |
|
|
|
|
|
|
|
|
| |
Provide extentions to <inttpes.h> PRIxxx constants for more POSIX types.
Start with existing definitions found in RTEMS Project owned code
in cpukit/.
updates #2983.
|
|
|
|
|
|
|
| |
Do not use our long file name entry count to optimize the file name
search. The Unicode comparison must be taken into account.
Update #2939.
|
|
|
|
|
|
| |
Obtain file system instance lock before member access.
Update #2937.
|
|
|
|
|
| |
The name "fat_entries" for long file name directory entries is quite
misleading.
|
|
|
|
| |
Update #2934.
|
|
|
|
| |
Simplify.
|
|
|
|
|
|
| |
Make sure that long file names work accross cluster boundaries.
Update #2929.
|
|
|
|
| |
Update #2929.
|
|
|
|
| |
Update #2929.
|
|
|
|
| |
Update #2929.
|
|
|
|
| |
Update #2929.
|
|
|
|
|
|
|
|
| |
Remove forced overwrite which leads to file data corruption. The logic
to determine a forced overwrite was fundamentally broken. For simplity,
disable this feature.
Update #2622.
|
|
|
|
|
|
|
|
| |
It is all right in case the result uses the full destination buffer.
Without this fix the handling of a maximum 8.3 short file name is
broken.
Update #2928.
|
|
|
|
|
|
|
|
|
| |
The second FAT entry contains a bit to indicate if the FAT32 filesystem
is not dirty and a bit to indicate if there was no IO error. Set both
bits for a fresh filesystem. This prevents a warning if mounted on
Windows.
Close #2913.
|
|
|
|
| |
Close #2755.
|
|
|
|
| |
Real implementation is provided by libbsd.
|
|
|
|
| |
Update #2388.
|
|
|
|
|
|
| |
For a filename match the entry must match without anything remaining.
Close #2908.
|
|
|
|
| |
Update #2803.
|
|
|
|
| |
Close #2700.
|
| |
|
|
|
|
| |
Update #2844.
|
|
|
|
|
|
| |
Add IO control to force a garbage collection.
Update #2844.
|
|
|
|
|
|
|
| |
Add IO control RTEMS_JFFS2_GET_INFO to get some JFFS2 filesystem
instance information.
Update #2844.
|
|
|
|
|
| |
This helps to use IMFS_make_generic_node() without pulling in the
complete IMFS implementation.
|
|
|
|
|
| |
Use the adjusted and not the requested memfile bytes per block.
Untangle dependencies.
|
|
|
|
| |
Ensure that we extract a node only from the right tree.
|
|
|
|
| |
This helps to detect double insert and extract errors.
|
| |
|
|
|
|
| |
closes #2756,
|
| |
|
|
|
|
| |
Close #2728.
|
|
|
|
| |
Close #2727.
|
|
|
|
|
| |
This change does not fix the printk format warnings rather
it ignores them.
|
|
|
|
|
|
|
| |
A cluster size > 32KiB resulted in an infinite loop in
fat_init_volume_info() due to an integer overflow.
Close #2717.
|
| |
|
|
|
|
|
|
| |
Drop superfluous <stdlib.h> include from <rtems/diskdevs.h> since this
leads to conflicts with the latest Newlib in case this header file is
used in the FreeBSD kernel space, e.g. for USB mass storage support.
|
|
|
|
| |
The permission is check by the upper layer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem exists for both RTEMS untar implementations and their
variants: Untar_FromMemory(), Untar_FromFile() and rtems_tarfs_load().
If filesystem object already exists at extracted directory path
then if it is directory, creation is ignored. Attempt
to delete/unlink object and make directory is tried for other cases.
This simple approach problem reported in ticket fixes #2413.
Behavior follows GNU tar and BSD tar practice for directories
but much more work is required to achieve full semantics
of the full featured tar implementation still.
|
| |
|