1io_uring_prep_symlinkat(3)      liburing Manual     io_uring_prep_symlinkat(3)
2
3
4

NAME

6       io_uring_prep_symlinkat - prepare a symlinkat request
7

SYNOPSIS

9       #include <fcntl.h>
10       #include <unistd.h>
11       #include <liburing.h>
12
13       void io_uring_prep_symlinkat(struct io_uring_sqe *sqe,
14                                    const char *target,
15                                    int newdirfd,
16                                    const char *linkpath);
17
18       void io_uring_prep_symlink(struct io_uring_sqe *sqe,
19                                  const char *target,
20                                  const char *linkpath);
21

DESCRIPTION

23       The  io_uring_prep_symlinkat(3)  function prepares a symlinkat request.
24       The submission queue entry sqe is setup  to  symlink  the  target  path
25       pointed  to  by target to the new destination indicated by newdirfd and
26       linkpath.
27
28       The io_uring_prep_symlink(3) function prepares a symlink  request.  The
29       submission  queue entry sqe is setup to symlink the target path pointed
30       to by target to the new destination indicated by linkpath  relative  to
31       the the current working directory. This function prepares an async sym‐
32       link(2) request. See that man page for details.
33
34       These functions prepare an async symlinkat(2)  or  symlink(2)  request.
35       See those man pages for details.
36
37

RETURN VALUE

39       None
40

ERRORS

42       The CQE res field will contain the result of the operation. See the re‐
43       lated man page for details on possible values. Note that where synchro‐
44       nous system calls will return -1 on failure and set errno to the actual
45       error value, io_uring never uses errno.  Instead it returns the negated
46       errno directly in the CQE res field.
47

NOTES

49       As with any request that passes in data in a struct, that data must re‐
50       main valid until the request has been successfully submitted.  It  need
51       not  remain  valid until completion. Once a request has been submitted,
52       the in-kernel state is stable. Very early kernels (5.4 and earlier) re‐
53       quired  state  to be stable until the completion occurred. Applications
54       can test for this behavior by inspecting the  IORING_FEAT_SUBMIT_STABLE
55       flag passed back from io_uring_queue_init_params(3).
56

SEE ALSO

58       io_uring_get_sqe(3), io_uring_submit(3), symlinkat(2), symlink(2)
59
60
61
62liburing-2.2                    March 13, 2022      io_uring_prep_symlinkat(3)
Impressum