|
constexpr | symlink_handle () |
| Default constructor.
|
|
constexpr | symlink_handle (native_handle_type h, dev_t devid, ino_t inode, flag flags=flag::none) |
| Construct a handle from a supplied native handle.
|
|
constexpr | symlink_handle (handle &&o) noexcept |
| Explicit conversion from handle permitted.
|
|
| symlink_handle (symlink_handle &&)=default |
| Move construction permitted.
|
|
| symlink_handle (const symlink_handle &)=delete |
| No copy construction (use clone() )
|
|
symlink_handle & | operator= (symlink_handle &&o) noexcept |
| Move assignment permitted.
|
|
symlink_handle & | operator= (const symlink_handle &)=delete |
| No copy assignment.
|
|
void | swap (symlink_handle &o) noexcept |
| Swap with another instance.
|
|
virtual result< void > | close () noexcept override |
| Immediately close the native handle type managed by this handle.
|
|
virtual result< symlink_handle > | reopen (mode mode_=mode::unchanged, deadline d=std::chrono::seconds(30)) const noexcept |
|
template<class... Args> |
bool | try_reopen (Args &&... args) noexcept |
|
template<class... Args, class Rep , class Period > |
bool | try_reopen_for (Args &&... args, const std::chrono::duration< Rep, Period > &duration) noexcept |
|
template<class... Args, class Clock , class Duration > |
bool | try_reopen_until (Args &&... args, const std::chrono::time_point< Clock, Duration > &timeout) noexcept |
|
virtual result< buffers_type > | read (io_request< buffers_type > req={}) noexcept |
|
virtual result< const_buffers_type > | write (io_request< const_buffers_type > req, deadline d=deadline()) noexcept |
|
flag | flags () const noexcept |
| The flags this handle was opened with.
|
|
| QUICKCPPLIB_BITFIELD_BEGIN_T (flag, uint16_t) |
| Bitwise flags which can be specified.
|
|
void | swap (handle &o) noexcept |
| Swap with another instance.
|
|
virtual result< path_type > | current_path () const noexcept |
|
result< handle > | clone () const noexcept |
|
virtual native_handle_type | release () noexcept |
| Release the native handle type managed by this handle.
|
|
bool | is_valid () const noexcept |
| True if the handle is valid (and usually open)
|
|
bool | is_readable () const noexcept |
| True if the handle is readable.
|
|
bool | is_writable () const noexcept |
| True if the handle is writable.
|
|
bool | is_append_only () const noexcept |
| True if the handle is append only.
|
|
virtual result< void > | set_append_only (bool enable) noexcept |
| EXTENSION: Changes whether this handle is append only or not.
|
|
bool | is_multiplexable () const noexcept |
| True if multiplexable.
|
|
bool | is_nonblocking () const noexcept |
| True if nonblocking.
|
|
bool | is_seekable () const noexcept |
| True if seekable.
|
|
bool | requires_aligned_io () const noexcept |
| True if requires aligned i/o.
|
|
bool | is_kernel_handle () const noexcept |
| True if native_handle() is a valid kernel handle.
|
|
bool | is_regular () const noexcept |
| True if a regular file or device.
|
|
bool | is_directory () const noexcept |
| True if a directory.
|
|
bool | is_symlink () const noexcept |
| True if a symlink.
|
|
bool | is_pipe () const noexcept |
| True if a pipe.
|
|
bool | is_socket () const noexcept |
| True if a socket.
|
|
bool | is_multiplexer () const noexcept |
| True if a multiplexer like BSD kqueues, Linux epoll or Windows IOCP.
|
|
bool | is_process () const noexcept |
| True if a process.
|
|
bool | is_section () const noexcept |
| True if a memory section.
|
|
bool | is_allocation () const noexcept |
| True if a memory allocation.
|
|
bool | is_path () const noexcept |
| True if a path or a directory.
|
|
bool | is_tls_socket () const noexcept |
| True if a TLS socket.
|
|
bool | is_http_socket () const noexcept |
| True if a HTTP socket.
|
|
caching | kernel_caching () const noexcept |
| Kernel cache strategy used by this handle.
|
|
bool | are_reads_from_cache () const noexcept |
| True if the handle uses the kernel page cache for reads.
|
|
bool | are_writes_durable () const noexcept |
| True if writes are safely on storage on completion.
|
|
bool | are_safety_barriers_issued () const noexcept |
| True if issuing safety fsyncs is on.
|
|
native_handle_type | native_handle () const noexcept |
| The native handle used by this handle.
|
|
dev_t | st_dev () const noexcept |
| Unless flag::disable_safety_unlinks is set, the device id of the file when opened.
|
|
ino_t | st_ino () const noexcept |
| Unless flag::disable_safety_unlinks is set, the inode of the file when opened. When combined with st_dev(), forms a unique identifer on this system.
|
|
unique_id_type | unique_id () const noexcept |
| A unique identifier for this handle across the entire system. Can be used in hash tables etc.
|
|
virtual result< path_handle > | parent_path_handle (deadline d=std::chrono::seconds(30)) const noexcept |
| Obtain a handle to the path currently containing this handle's file entry.
|
|
template<class... Args> |
bool | try_parent_path_handle (Args &&... args) noexcept |
|
template<class... Args, class Rep , class Period > |
bool | try_parent_path_handle_for (Args &&... args, const std::chrono::duration< Rep, Period > &duration) noexcept |
|
template<class... Args, class Clock , class Duration > |
bool | try_parent_path_handle_until (Args &&... args, const std::chrono::time_point< Clock, Duration > &timeout) noexcept |
|
virtual result< void > | relink (const path_handle &base, path_view_type path, bool atomic_replace=true, deadline d=std::chrono::seconds(30)) noexcept |
| Relinks the current path of this open handle to the new path specified. If atomic_replace is true, the relink atomically and silently replaces any item at the new path specified. This operation is both atomic and matching POSIX behaviour even on Microsoft Windows where no Win32 API can match POSIX semantics.
|
|
template<class... Args> |
bool | try_relink (Args &&... args) noexcept |
|
template<class... Args, class Rep , class Period > |
bool | try_relink_for (Args &&... args, const std::chrono::duration< Rep, Period > &duration) noexcept |
|
template<class... Args, class Clock , class Duration > |
bool | try_relink_until (Args &&... args, const std::chrono::time_point< Clock, Duration > &timeout) noexcept |
|
virtual result< void > | link (const path_handle &base, path_view_type path, deadline d=std::chrono::seconds(30)) noexcept |
| Links the inode referred to by this open handle to the path specified. The current path of this open handle is not changed, unless it has no current path due to being unlinked.
|
|
template<class... Args> |
bool | try_link (Args &&... args) noexcept |
|
template<class... Args, class Rep , class Period > |
bool | try_link_for (Args &&... args, const std::chrono::duration< Rep, Period > &duration) noexcept |
|
template<class... Args, class Clock , class Duration > |
bool | try_link_until (Args &&... args, const std::chrono::time_point< Clock, Duration > &timeout) noexcept |
|
virtual result< void > | unlink (deadline d=std::chrono::seconds(30)) noexcept |
| Unlinks the current path of this open handle, causing its entry to immediately disappear from the filing system.
|
|
template<class... Args> |
bool | try_unlink (Args &&... args) noexcept |
|
template<class... Args, class Rep , class Period > |
bool | try_unlink_for (Args &&... args, const std::chrono::duration< Rep, Period > &duration) noexcept |
|
template<class... Args, class Clock , class Duration > |
bool | try_unlink_until (Args &&... args, const std::chrono::time_point< Clock, Duration > &timeout) noexcept |
|
virtual result< span< path_view_component > > | list_extended_attributes (span< byte > tofill) const noexcept |
| Fill the supplied buffer with the names of all extended attributes set on this file or directory, returning a span of path view components.
|
|
virtual result< span< byte > > | get_extended_attribute (span< byte > tofill, path_view_component name) const noexcept |
| Retrieve the value of an extended attribute set on this file or directory.
|
|
virtual result< void > | set_extended_attribute (path_view_component name, span< const byte > value) noexcept |
| Sets the value of an extended attribute on this file or directory.
|
|
virtual result< void > | remove_extended_attribute (path_view_component) noexcept |
| Removes the extended attribute set on this file or directory.
|
|
result< size_t > | copy_extended_attributes (const fs_handle &src, bool replace_all_local_attributes=false) noexcept |
| Copies the extended attributes from one entity to another, optionally replacing all the extended attributes on the destination.
|
|
A handle to an inode which redirects to a different path.
Microsoft Windows and Linux provide the ability to open the contents of a symbolic link directly, for those platforms this handle works exactly like any ordinary handle. For other POSIX platforms without proprietary extensions, it is not possible to get a valid file descriptor to the contents of a symlink, and in this situation the native handle returned will be -1
and the preprocessor macro LLFIO_SYMLINK_HANDLE_IS_FAKED
will be non-zero.
If LLFIO_SYMLINK_HANDLE_IS_FAKED
is on, the handle is race free up to the containing directory only. If a third party relocates the symbolic link into a different directory, and race free checking is enabled, this class will simply refuse to work with errc::no_such_file_or_directory
as it no longer has any way of finding the symbolic link. You should take care that this does not become a denial of service attack.
On Microsoft Windows, there are many kinds of symbolic link: this implementation supports directory junctions, and NTFS symbolic links. Reads of any others will return an error code comparing equal to errc::protocol_not_supported
. One should note that modifying symbolic links was not historically permitted by users with ordinary permissions on Microsoft Windows, however recent versions of Windows 10 do support symbolic links for ordinary users. All versions of Windows support directory symbolic links (junctions), these work for all users in any configuration.
(Note that to create a directory junction on Windows, first create a directory, open that empty directory for modification using symlink_handle, then write using symlink_type::win_junction
)
llfio_v2_xxx::handle::QUICKCPPLIB_BITFIELD_BEGIN_T |
( |
flag |
, |
|
|
uint16_t |
|
|
) |
| |
|
inlineinherited |
Bitwise flags which can be specified.
< No flags
Unlinks the file on handle close. On POSIX, this simply unlinks whatever is pointed to by path()
upon the call of close()
if and only if the inode matches. On Windows, if you are on Windows 10 1709 or later, exactly the same thing occurs. If on previous editions of Windows, the file entry does not disappears but becomes unavailable for anyone else to open with an errc::resource_unavailable_try_again
error return. Because this is confusing, unless the win_disable_unlink_emulation
flag is also specified, this POSIX behaviour is somewhat emulated by LLFIO on older Windows by renaming the file to a random name on close()
causing it to appear to have been unlinked immediately.
Some kernel caching modes have unhelpfully inconsistent behaviours in getting your data onto storage, so by default unless this flag is specified LLFIO adds extra fsyncs to the following operations for the caching modes specified below: truncation of file length either explicitly or during file open. closing of the handle either explicitly or in the destructor.
Additionally on Linux only to prevent loss of file metadata: On the parent directory whenever a file might have been created. On the parent directory on file close.
This only occurs for these kernel caching modes: caching::none caching::reads caching::reads_and_metadata caching::safety_barriers
file_handle::unlink()
could accidentally delete the wrong file if someone has renamed the open file handle since the time it was opened. To prevent this occuring, where the OS doesn't provide race free unlink-by-open-handle we compare the inode of the path we are about to unlink with that of the open handle before unlinking.
- Warning
- This does not prevent races where in between the time of checking the inode and executing the unlink a third party changes the item about to be unlinked. Only operating systems with a true race-free unlink syscall are race free.
Ask the OS to disable prefetching of data. This can improve random i/o performance.
Ask the OS to maximise prefetching of data, possibly prefetching the entire file into kernel cache. This can improve sequential i/o performance.
< See the documentation for unlink_on_first_close
Microsoft Windows NTFS, having been created in the late 1980s, did not originally implement extents-based storage and thus could only represent sparse files via efficient compression of intermediate zeros. With NTFS v3.0 (Microsoft Windows 2000), a proper extents-based on-storage representation was added, thus allowing only 64Kb extent chunks written to be stored irrespective of whatever the maximum file extent was set to.
For various historical reasons, extents-based storage is disabled by default in newly created files on NTFS, unlike in almost every other major filing system. You have to explicitly "opt in" to extents-based storage.
As extents-based storage is nearly cost free on NTFS, LLFIO by default opts in to extents-based storage for any empty file it creates. If you don't want this, you can specify this flag to prevent that happening.
Filesystems tend to be embarrassingly parallel for operations performed to different inodes. Where LLFIO performs i/o to multiple inodes at a time, it will use OpenMP or the Parallelism or Concurrency standard library extensions to usually complete the operation in constant rather than linear time. If you don't want this default, you can disable default using this flag.
Microsoft Windows NTFS has the option, when creating a directory, to set whether leafname lookup will be case sensitive. This is the only way of getting exact POSIX semantics on Windows without resorting to editing the system registry, however it also affects all code doing lookups within that directory, so we must default it to off.
Create the handle in a way where i/o upon it can be multiplexed with other i/o on the same initiating thread of execution i.e. you can perform more than one read concurrently, without using threads. The blocking operations .read()
and .write()
may have to use a less efficient, but cancellable, blocking implementation for handles created in this way. On Microsoft Windows, this creates handles with OVERLAPPED
semantics. On POSIX, this creates handles with nonblocking semantics for non-file handles such as pipes and sockets, however for file, directory and symlink handles it does not set nonblocking, as it is non-portable.
< Using insane POSIX byte range locks
< This is an inode created with no representation on the filing system
110 {
112
113
114
115
116
117
118
119
120
121 unlink_on_first_close = uint16_t(1U << 0U),
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140 disable_safety_barriers = uint16_t(1U << 2U),
141
142
143
144
145
146
147
148
149 disable_safety_unlinks = uint16_t(1U << 3U),
150
151
152
153 disable_prefetching = uint16_t(1U << 4U),
154
155
156
157 maximum_prefetching = uint16_t(1U << 5U),
158
159 win_disable_unlink_emulation = uint16_t(1U << 9U),
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175 win_disable_sparse_file_creation = uint16_t(1U << 10U),
176
177
178
179
180
181
182 disable_parallelism = uint16_t(1U << 11U),
183
184
185
186
187
188 win_create_case_sensitive_directory = uint16_t(1U << 12U),
189
190
191
192
193
194
195
196
197
198
199 multiplexable = uint16_t(1U << 13U),
200
201
202
203 byte_lock_insanity = uint16_t(1U << 14U),
204 anonymous_inode = uint16_t(1U << 15U)
205 } QUICKCPPLIB_BITFIELD_END(flag)
@ none
No ability to read or write anything, but can synchronise (SYNCHRONIZE or 0)
virtual result< void > llfio_v2_xxx::fs_handle::set_extended_attribute |
( |
path_view_component |
name, |
|
|
span< const byte > |
value |
|
) |
| |
|
virtualnoexceptinherited |
Sets the value of an extended attribute on this file or directory.
To prevent collision in a globally visible resource, there is a convention whereby you ought to namespace the names of your values as namespace.attribute
e.g. appname.setting
to prevent unintentional collision with other programs. Obviously, do choose a unique appname
if there is any chance another program might use the same namespace name.
On POSIX, there are additional namespacing requirements: before your value name, you need to prefix one of user
or system
, so the actual name you might set would be user.appname.propname
. Windows does not have the user
/system
prefix requirement, but it does no harm to do the exact same on Windows as on POSIX.
The host OS and target filing system choose the limits on value size, and will fail accordingly. Some impose a maximum of 64Kb for all names and values per inode, others have a 4Kb maximum value size, there are lots of combinations. You are probably safest not setting many names, and keep the values short.
- Warning
- Extended attributes are 'brittle' because they can get silently wiped at any moment. Never store anything in extended attributes which cannot be recalculated if missing. The ideal use case for extended attributes is as a cache of additional metadata about a file or directory e.g. "I last checked this directory at timestamp X", or "the MD5 hash at last modified
timestamp X for this file was Y". Also remember that other processes can and do arbitrarily modify extended attributes concurrent to you.
Windows only
This API is implemented as file alternate data streams, rather than the Extended Attributes API as accessed via NtSetEaFile()
and NtQueryEaFile()
(which actually modify the file alternate data stream ::$EA
in any case).
The reason why is that NtSetEaFile()
can only append new records to EA storage. It cannot deallocate any existing EA records, if you try to do so you will get STATUS_EA_CORRUPT_ERROR
. You can append setting the same name to a different value, which can include a null value which then appears as if the name is no longer there. But there is a cap of 64kB for the EA record, and once it is consumed, it is gone forever for that inode.
Obviously that doesn't map at all well onto POSIX extended attributes, where you can set the value of an attribute as frequently as you like. The closest equivalent on Windows is therefore file alternate data streams, even though the attribute's value is then worked with as a whole proper file with all the attendant performance consequences.
As a result, name
must be a valid filename and not contain any characters not permitted in a filename. We use the NT API here, so the character restrictions are far fewer than for the Win32 API e.g. single character names do NOT cause misoperation like on Win32.