| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 2957 |
5853 d 2 h |
jermar |
/trunk/uspace/srv/vfs/ |
Cram VFS_MOUNT into one message. This creates a hidden demand for the sixth IPC
argument as there might be a desire to pass some options/flags in the future. |
|
| 2821 |
5893 d 21 h |
jermar |
/trunk/uspace/srv/vfs/ |
Update comment. |
|
| 2788 |
5904 d 14 h |
jermar |
/trunk/uspace/ |
Return EBUSY if trying to mount something over an already mounted root FS.
(Contributed by Tim Post) |
|
| 2770 |
5921 d 2 h |
jermar |
/trunk/uspace/ |
Introduce fs_handle_t, dev_handle_t and fs_index_t. |
|
| 2769 |
5922 d 0 h |
jermar |
/trunk/uspace/srv/vfs/ |
VFS index needs to be treated as uint64_t. |
|
| 2768 |
5922 d 2 h |
jermar |
/trunk/uspace/srv/vfs/ |
Fibril serialization is required when two file systems register contemporarily. |
|
| 2766 |
5923 d 2 h |
jermar |
/trunk/uspace/srv/vfs/ |
Grab the nodes_futex when manipulating node link counts in rename() and
_unlink().
Fix VFS futex definitions and declarations by replacing atomic_t by futex_t. |
|
| 2763 |
5923 d 5 h |
jermar |
/trunk/uspace/ |
Support for rename(). |
|
| 2753 |
5930 d 1 h |
jermar |
/trunk/uspace/ |
Move canonify() to libc so that it can be used also on the libc side. |
|
| 2752 |
5930 d 7 h |
jermar |
/trunk/uspace/srv/vfs/ |
Make VFS canonify path names on lookup. |
|
| 2751 |
5931 d 5 h |
jermar |
/trunk/uspace/ |
Add canonify() for file system path canonization.
Not yet used by VFS. |
|
| 2749 |
5933 d 1 h |
jermar |
/trunk/uspace/srv/vfs/ |
contents_rwlock should not be acquired as a futex but rather as a rwlock. |
|
| 2748 |
5933 d 1 h |
jermar |
/trunk/uspace/srv/vfs/ |
Support for O_TRUNC. |
|
| 2742 |
5936 d 0 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(). |
|
| 2740 |
5942 d 0 h |
jermar |
/trunk/uspace/srv/vfs/ |
Initialize the VFS node properly. |
|
| 2735 |
5944 d 6 h |
jermar |
/trunk/uspace/ |
Support for rmdir(), unlink() and the respective VFS operations. |
|
| 2734 |
5944 d 8 h |
jermar |
/trunk/uspace/ |
Support for close(). |
|
| 2731 |
5944 d 9 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 |
5945 d 11 h |
jermar |
/trunk/uspace/srv/ |
Introduce the notion of VFS node link counts. |
|
| 2710 |
5965 d 3 h |
jermar |
/trunk/uspace/ |
VFS_WRITE and tmpfs_write fixes. |
|
| 2709 |
5965 d 6 h |
jermar |
/trunk/uspace/srv/vfs/ |
VFS_OPEN and VFS_WRITE now understand O_APPEND. |
|
| 2708 |
5965 d 6 h |
jermar |
/trunk/uspace/ |
VFS_OPEN now understands O_CREAT and O_EXCL. |
|
| 2707 |
5965 d 7 h |
jermar |
/trunk/uspace/ |
Support for mkdir(). |
|
| 2704 |
5966 d 10 h |
jermar |
/trunk/uspace/srv/vfs/ |
Additional VFS lookup flags. |
|
| 2700 |
5973 d 9 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). |
|
| 2698 |
5974 d 4 h |
jermar |
/trunk/uspace/srv/vfs/ |
Small fix for VFS_TRUNCATE. Move lookup and registration code to separate
modules. |
|
| 2693 |
5979 d 9 h |
jermar |
/trunk/uspace/ |
Add ftruncate() and support for VFS_TRUNCATE to VFS and TMPFS. |
|
| 2691 |
5983 d 3 h |
jermar |
/trunk/uspace/srv/vfs/ |
Improve the API for converting (VFS triplets, size) to VFS nodes by introducing
a new type for results of vfs_lookup_internal(). |
|
| 2690 |
5984 d 0 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. |
|
| 2689 |
5984 d 1 h |
jermar |
/trunk/uspace/srv/vfs/ |
Merge all VFS operations into one file. |
|
| 2688 |
5984 d 2 h |
jermar |
/trunk/uspace/ |
Make uspace rwlock API naming conventions consistent with kernel rwlock API. |
|
| 2687 |
5984 d 2 h |
jermar |
/trunk/uspace/srv/ |
Management of the cached VFS node size. |
|
| 2684 |
5986 d 3 h |
jermar |
/trunk/ |
Add libc and VFS implementation of lseek(), VFS_SEEK resp.
Add the size member to the VFS node structure (not yet initialized). |
|
| 2683 |
5986 d 6 h |
jermar |
/trunk/uspace/srv/vfs/ |
Introduce the open file lock. Modify vfs_rdwr() to take this lock into account
when reading or writing from/to an open file. |
|
| 2682 |
5986 d 8 h |
jermar |
/trunk/uspace/ |
Fix type in declaration of VFS node rwlock.
Introduce a dedicated type for futexes. Make the existing futex code use this
newly introduced type and fix formatting in futex.c. |
|
| 2681 |
5986 d 9 h |
jermar |
/trunk/uspace/ |
Turn the namespace futex into rwlock. |
|
| 2680 |
5986 d 10 h |
jermar |
/trunk/uspace/ |
Add basic rwlock API for uspace so that VFS can be designed/implemented using
this API. So far, the implementation of this API merely wraps futexes into
rwlocks. Real rwlocks are wanted by ticket #54.
Using the new rwlock API, replace the VFS node content futex with an rwlock.
Lock the contents rwlock as reader on reads and as writer on writes. |
|
| 2679 |
5990 d 2 h |
jermar |
/trunk/uspace/srv/vfs/ |
Rename unlink_futex to namespace_futex and introduce a new futex for serializing
concurrent access to a VFS node's contents by multiple clients. |
|
| 2678 |
5992 d 5 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. |
|
| 2677 |
5992 d 6 h |
jermar |
/trunk/ |
Rename IPC_M_AS_AREA_SEND to IPC_M_SHARE_OUT. Rename IPC_M_AS_AREA_RECV to
IPC_M_SHARE_IN. Provide user-friendly wrappers for these methods so that even
dummies can get it right. Some applications using simpler protocols still use
these methods directly. |
|