a0c734da01
Documentation & minor cleanup
2024-12-24 14:26:19 +00:00
c22fb790b8
Fix parallel test runs
2024-10-29 12:22:15 +03:00
469db981a4
Fix a fuse bug
...
Create reply contains flags but those are not O_* passed in by request.
Those are FOPEN_* fuse-specific flags describing new file's mode (caching,
passthrough etc).
2024-10-27 20:45:25 +03:00
43ec8d1417
Clean up indentation using let-else and format.
2024-09-02 00:46:48 +03:00
3baf131419
Fixed no_std regression in 0.6.5
...
And bumped some dependencies and fixed some warnings
2024-06-29 20:52:24 +03:00
6a6bd97910
Add redoxfs fuzzer for FUSE interface
2024-06-27 16:05:42 +00:00
8a31d1b6a6
Use positioned IO scheme interface.
2024-06-12 17:37:06 +02:00
3800bf1510
Switch to v2 packet interface.
2024-06-11 16:10:34 +02:00
15f3c909c7
Switch almost fully to libredox.
2024-03-18 17:28:43 +01:00
efb29941f5
Handle but don't impl scheme cancellation.
2024-03-16 09:30:14 +01:00
5156ebd179
use new path formatting and conversion code
2024-03-01 06:24:13 -08:00
644a2d2081
Fix clippy lints
2024-02-14 12:38:02 -07:00
4e0ab54567
Make everything scale with block size and format
2024-02-14 10:15:26 -07:00
5f00068c26
Merge branch 'redox-path' into 'master'
...
Use new path format
See merge request redox-os/redoxfs!66
2024-02-09 15:06:51 +00:00
c1601fe16c
Use new path format
2024-02-09 15:06:51 +00:00
e3f0fe6ef9
Remove mmap prints
2024-02-08 17:34:20 -07:00
944b175a6e
fix symbolic links plus general cleanup
2024-01-03 16:39:58 +00:00
9a8437f468
0.5.10: Squash allocations and sync on unmount
2023-12-12 11:10:04 -07:00
ae715277f3
Cache current fmap size
2023-11-15 12:20:15 -07:00
6234d76e8d
Fix mremap usage.
2023-08-03 12:38:19 +02:00
ae1f15a449
Offset-based file mmap.
2023-07-26 16:06:53 +02:00
5db0da52e2
WIP: Use improved mmap interface.
2023-07-20 16:58:58 +02:00
13948965fa
Fix unnecessary mutable variable warning
2023-05-08 13:11:16 +01:00
62e59e1006
Migrate from fuse to fuser
2023-03-18 08:53:54 +00:00
73c3d8bb79
Allow root to remove other users' files.
2023-03-01 17:24:37 +01:00
9215e32254
Implement frename
2022-04-07 19:57:09 -06:00
419bd0f0a6
Fix for some kinds of symbolic links
2022-04-06 18:17:23 -06:00
731b97262b
RedoxFS 0.5.0
...
Significant re-design to use copy-on-write and hashes for all data
2022-03-11 09:01:47 -07:00
cfe5841646
0.4.4 - no_std support
2022-02-05 20:28:11 -07:00
6d9a53c956
Update dependencies
2021-04-28 20:54:39 -06:00
5d4ed0831a
0.4.3 - update redox_syscall
2020-12-16 10:43:30 -07:00
c990fa9a45
0.4.1 - Support rename in fuse
2020-03-13 20:06:01 -06:00
58f2d28ff5
Format the codebase
2020-01-20 15:00:26 -05:00
d2256b3eb3
Add tracking of access times
...
Add the atime field, which tracks the last access time. Only reads
update the atime.
**BREAKING CHANGE**: One less extent available per block, 4 more bytes
for node names.
2020-01-20 16:56:51 +00:00
924adef1dc
Update path after frename
2019-08-11 15:30:09 +05:30
602a63acf6
Return EXDEV to tell kernel to resolve cross-scheme links
2019-07-23 21:05:54 -06:00
43533e8dc7
Merge branch 'jD91mZM2/redoxfs-master' into HEAD
2019-07-20 19:41:48 -06:00
4578a22297
Tests
2019-07-20 17:08:33 +00:00
5e5656f110
Make mount points not require an extra reference
2019-07-18 21:36:16 -06:00
ec072bb718
Return correct error for fevent on files
2019-04-28 13:32:43 -06:00
015d352e33
Fixes for Redox when part of unix target family
2019-04-23 13:55:46 -06:00
ff17fed199
Reimplement fmap/funmap using improvements to kernel
2019-04-06 20:11:51 -06:00
cb2bcf9f59
Fix redoxfs fmap using incorrect offset
2019-04-02 20:18:40 -06:00
b4df131aff
Fix disk usage calculation
2019-02-24 20:46:21 -07:00
b32a421b97
Correct access control
2018-12-30 09:58:58 -07:00
69d6cc05de
Update fmap support
2018-12-30 09:47:33 -07:00
3ae32d9901
Reduce diff - remove dirty flag as it could be added in a separate change
2018-12-08 08:47:28 -07:00
87ecce9e44
Cleanup and use unmount flag inside of Redox scheme processing function
2018-12-08 08:10:23 -07:00
f96d330993
wip implementation of unmounting and dirty bits for redoxfs
2018-12-06 11:09:41 -05:00
79cef7c034
Adopt linux' O_APPEND behavior
...
According to `man open`:
> The file is opened in append mode. Before each write(2), the file offset
is positioned at the end of the file, as if with lseek(2). The modi‐
fication of the file offset and the write operation are performed as a
single atomic step.
2018-10-07 15:22:13 +02:00
rm-dr