|author||Jens Axboe <firstname.lastname@example.org>||2020-02-01 11:04:41 -0700|
|committer||Jens Axboe <email@example.com>||2020-02-01 11:04:41 -0700|
man/io_uring_enter.2: clarify how/when IOSQE_IO_LINK are terminated
Signed-off-by: Jens Axboe <firstname.lastname@example.org>
1 files changed, 7 insertions, 1 deletions
diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
index ca8a736..94ab625 100644
@@ -545,7 +545,13 @@ of the chain is denoted by the first SQE that does not have this flag set.
This flag has no effect on previous SQE submissions, nor does it impact SQEs
that are outside of the chain tail. This means that multiple chains can be
executing in parallel, or chains and individual SQEs. Only members inside the
-chain are serialized. Available since 5.3.
+chain are serialized. A chain of SQEs will be broken, if any request in that
+chain ends in error. io_uring considers any unexpected result an error. This
+means that, eg, a short read will also terminate the remainder of the chain.
+If a chain of SQE links is broken, the remaining unstarted part of the chain
+will be terminated and completed with
+as the error code. Available since 5.3.
Like IOSQE_IO_LINK, but it doesn't sever regardless of the completion result.