| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 2828 |
5973 d 13 h |
jermar |
/trunk/uspace/srv/fs/fat/ |
BPS read from FAT bootsector is little-endian. It must converted to host
endianity before being used. |
|
| 2822 |
5974 d 12 h |
jermar |
/trunk/uspace/srv/fs/fat/ |
Introduce and also use the foundation of block cache API in FAT's match
operation. |
|
| 2798 |
5978 d 17 h |
jermar |
/trunk/uspace/ |
Replace all endian.h in uspace with a copy of the kernel's respective byteorder.h. |
|
| 2796 |
5979 d 17 h |
jermar |
/trunk/uspace/srv/fs/fat/ |
Convert FAT on-disk metadata from little-endian to native representation. |
|
| 2793 |
5979 d 18 h |
jermar |
/trunk/uspace/srv/fs/fat/ |
First untested bits of FAT lookup support. |
|
| 2792 |
5979 d 18 h |
jermar |
/trunk/uspace/ |
libfs' node_get() operation does not need the file system handle. |
|
| 2791 |
5982 d 15 h |
jermar |
/trunk/uspace/ |
Make libfs_lookup() more generic. |
|
| 2789 |
5985 d 5 h |
jermar |
/trunk/uspace/srv/fs/fat/ |
Fix FAT boot sector definition and introduce the FAT in-core node type. |
|
| 2770 |
6001 d 17 h |
jermar |
/trunk/uspace/ |
Introduce fs_handle_t, dev_handle_t and fs_index_t. |
|
| 2763 |
6003 d 20 h |
jermar |
/trunk/uspace/ |
Support for rename(). |
|
| 2760 |
6006 d 15 h |
jermar |
/trunk/uspace/ |
Support for multiple TMPFS node names. |
|
| 2758 |
6007 d 15 h |
jermar |
/trunk/uspace/ |
No need to keep the parent pointer in the TMPFS node. Moreover, other file
systems won't have it either. Finally, if TMPFS is to support hardlinks, there
can be multiple parents. |
|
| 2757 |
6007 d 17 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Set the TMPFS root node's link count to 1. |
|
| 2756 |
6007 d 18 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Introduce real link counts for TMPFS. |
|
| 2747 |
6014 d 15 h |
jermar |
/trunk/uspace/ |
Move the core lookup logic from TMPFS to libfs. |
|
| 2742 |
6016 d 15 h |
jermar |
/trunk/uspace/srv/ |
Separate creation of a TMPFS node and its linking in the file system name space.
Rename VFS_FREE to VFS_DESTROY and destroy_node() to unlink_node(). |
|
| 2739 |
6022 d 16 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Remove duplicate initialization. |
|
| 2736 |
6024 d 17 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Unlink a TMPFS node more thoroughly. |
|
| 2735 |
6024 d 21 h |
jermar |
/trunk/uspace/ |
Support for rmdir(), unlink() and the respective VFS operations. |
|
| 2733 |
6024 d 23 h |
jermar |
/trunk/uspace/ |
Add TMPFS support for destroying leaf links in the file system namespace. |
|
| 2732 |
6025 d 0 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
When freeing up a TMPFS node, it should also be removed from the dentries hash table. |
|
| 2731 |
6025 d 0 h |
jermar |
/trunk/uspace/srv/ |
Add the VFS_FREE operation. This operation frees up whatever resources used by
a file system node for which there is no name (i.e. an unlinked node).
Cleanup VFS operations enums and remove unneeded VFS operations. |
|
| 2730 |
6026 d 2 h |
jermar |
/trunk/uspace/srv/ |
Introduce the notion of VFS node link counts. |
|
| 2728 |
6030 d 16 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Descend vs. descent. |
|
| 2711 |
6045 d 18 h |
jermar |
/trunk/uspace/ |
Remove the debugging hack from tmpfs_init(), which created several files and
directories on the filesystem. TMPFS is now self-sufficient enough to be able
to create its content via the standard VFS interface. |
|
| 2710 |
6045 d 19 h |
jermar |
/trunk/uspace/ |
VFS_WRITE and tmpfs_write fixes. |
|
| 2707 |
6045 d 23 h |
jermar |
/trunk/uspace/ |
Support for mkdir(). |
|
| 2706 |
6046 d 3 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Move handling of the miss on excessive components out of the main loop in
tmpfs_lookup. |
|
| 2705 |
6046 d 15 h |
jermar |
/trunk/uspace/ |
More elegant, flexible and complete version of tmpfs_lookup. |
|
| 2700 |
6054 d 0 h |
jermar |
/trunk/uspace/ |
Introduce the notion of lflag (i.e. lookup flags) to support the ability to
limit the scope of VFS node types that can be opened by open() and opendir(). In
the future, lflag will also specify actions for VFS_LOOKUP handlers that will be
carried out in situations such as the VFS node is not found (e.g. implementation
of mkdir() and open() with O_CREAT in oflag). |
|
| 2699 |
6054 d 14 h |
jermar |
/trunk/uspace/ |
Finish implementation of readdir(). Functions from this family are implemented
via using file descriptors for directories. For example, readdir() is
implemented as read() from an open directory. Of course, FS implementations
must understand that they are asked to read a directory and behave accordingly. |
|
| 2693 |
6060 d 0 h |
jermar |
/trunk/uspace/ |
Add ftruncate() and support for VFS_TRUNCATE to VFS and TMPFS. |
|
| 2690 |
6064 d 16 h |
jermar |
/trunk/uspace/srv/ |
Make a distinction between VFS operations that are common to VFS and FS
implementations, operations that are VFS only and operations that are FS
implementations only. |
|
| 2687 |
6064 d 17 h |
jermar |
/trunk/uspace/srv/ |
Management of the cached VFS node size. |
|
| 2686 |
6064 d 18 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Previous commit was toxic. When emulating gaps, zero out the reallocated buffer, not the original one. |
|
| 2685 |
6064 d 18 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
TMPFS must handle file gaps. |
|
| 2678 |
6072 d 20 h |
jermar |
/trunk/uspace/ |
The IPC_M_SHARE_* and IPC_M_DATA_* calls pass through 3 stages. Rename the send,
receive and deliver wrappers to names ending with 'start', 'receive' and
'finalize', respectively. This should make it clearer for dummies. |
|
| 2676 |
6073 d 3 h |
jermar |
/trunk/ |
Simplify the IPC_M_DATA_WRITE protocol. Do not pass the source address space
virtual address to the recipient. This feature was not used anyway. Now
IPC_M_DATA_WRITE and IPC_M_DATA_READ are feature-aligned. |
|
| 2673 |
6073 d 16 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Rename variable from 'size' to 'len'. |
|
| 2667 |
6078 d 13 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
The previous commit was not entirely sane.
Handle VFS_WRITE correctly when the file doesn't grow.
Handle it correctly also when the file grows. |
|