axboe-liburing 2.15.2

Low-level io_uring interface, transliterated from Jens Axboe's liburing.
Documentation
Prepare an unlinkat request

# DESCRIPTION

The [io_uring_prep_unlinkat] function prepares an unlinkat request.
The submission queue entry *sqe* is setup to use the directory file
descriptor pointed to by *dirfd* to start an unlinkat operation on the
path identified by *path* and using the flags given in *flags*.

The [io_uring_prep_unlink] function prepares an unlink request. The
submission queue entry *sqe* is setup to start an unlinkat operation on
the path identified by *path* relative to the current working directory
and using the flags given in *flags*.

These functions prepare an async [unlinkat](https://man7.org/linux/man-pages/man2/unlinkat.2.html) or [unlink](https://man7.org/linux/man-pages/man2/unlink.2.html)
request. See those man pages for details.

# RETURN VALUE

None

# ERRORS

The CQE *res* field will contain the result of the operation. See the
related man page for details on possible values. Note that where
synchronous system calls will return **-1** on failure and set *errno*
to the actual error value, io_uring never uses *errno*. Instead it
returns the negated *errno* directly in the CQE *res* field.

# NOTES

As with any request that passes in data in a struct, that data must
remain valid until the request has been successfully submitted. It need
not remain valid until completion. Once a request has been submitted,
the in-kernel state is stable. Very early kernels (5.4 and earlier)
required state to be stable until the completion occurred. Applications
can test for this behavior by inspecting the
**IORING_FEAT_SUBMIT_STABLE** flag passed back from
[io_uring_queue_init_params].

# SEE ALSO

[io_uring_get_sqe], [io_uring_submit], [unlinkat](https://man7.org/linux/man-pages/man2/unlinkat.2.html),
[unlink](https://man7.org/linux/man-pages/man2/unlink.2.html)