summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2020-02-11 08:55:35 -0700
committerJens Axboe <axboe@kernel.dk>2020-02-11 08:57:32 -0700
commit797e50925bf01d249ede445b3148953b91b1049e (patch)
treeef517288f962d12cc254a43820c0e36e5f6415b4
parent3e63af4f252e1dfc2cb736863d8db4a3821f48e4 (diff)
downloadliburing-797e50925bf01d249ede445b3148953b91b1049e.tar.gz
liburing-797e50925bf01d249ede445b3148953b91b1049e.tar.bz2
man/io_uring_setup.2: document IORING_FEAT_CUR_PERSONALITY
Signed-off-by: Jens Axboe <axboe@kernel.dk>
-rw-r--r--man/io_uring_setup.216
1 files changed, 16 insertions, 0 deletions
diff --git a/man/io_uring_setup.2 b/man/io_uring_setup.2
index 27cf864..4057e4b 100644
--- a/man/io_uring_setup.2
+++ b/man/io_uring_setup.2
@@ -194,6 +194,22 @@ with
with the caveat that if the application has multiple reads or writes in flight,
then the end result will not be as expected. This is similar to threads sharing
a file descriptor and doing IO using the current file position.
+.TP
+.B IORING_FEAT_CUR_PERSONALITY
+If this flag is set, then io_uring guarantees that both sync and async
+execution of a request assumes the credentials of the task that called
+.I
+io_uring_enter(2)
+to queue the requests. If this flag isn't set, then requests are issued with
+the credentials of the task that originally registered the io_uring. If only
+one task is using a ring, then this flag doesn't matter as the credentials
+will always be the same. Note that this is the default behavior, tasks can
+still register different personalities through
+.I
+io_uring_register(2)
+with
+.B IORING_REGISTER_PERSONALITY
+and specify the personality to use in the sqe.
.PP
The rest of the fields in the